Windows position control for phone applications

ABSTRACT

Methods and devices for selectively presenting a user interface for a phone application are provided. More particularly, a change in the display mode of a multiple screen device can be determined. More particularly, a presentation of a user interface for an in-process call of a phone application can be retained after receiving a flick in an off-screen gesture area of the device. However, the user interface moves from a first screen to a second screen (or vice versa) in response to receiving the flick. The user interface provides detail information about a phone call that is currently in-process.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims the benefits of and priority, under 35U.S.C. §119(e), to U.S. Provisional Application Ser. No. 61/539,884,filed Sep. 27, 2011, entitled “MOBILE DEVICE.” Further, under 35 U.S.C.§120, the present application is a Continuation-in-Part of and claimspriority to U.S. patent application Ser. No. 13/222,970, titled “WINDOWSTACK MODELS FOR MULTI-SCREEN DISPLAYS,” having a filing date of Aug.31, 2011, which in turn claims priority, under 35 U.S.C. §119(e), toU.S. Provisional Application Ser. Nos. 61/389,000, filed Oct. 1, 2010,entitled “DUAL DISPLAY WINDOWING SYSTEM;” 61/389,117, filed Oct. 1,2010, entitled “MULTI-OPERATING SYSTEM PORTABLE DOCKETING DEVICE;”61/389,087, filed Oct. 1, 2010, entitled “TABLET COMPUTING USERINTERFACE.” All of the above applications are incorporated herein byreference in their entirety for all that they teach and for allpurposes.

BACKGROUND

A substantial number of handheld computing devices, such as cellularphones, tablets, and E-Readers, make use of a touch screen display notonly to deliver display information to the user but also to receiveinputs from user interface commands. While touch screen displays mayincrease the configurability of the handheld device and provide a widevariety of user interface options, this flexibility typically comes at aprice. The dual use of the touch screen to provide content and receiveuser commands, while flexible for the user, may obfuscate the displayand cause visual clutter, thereby leading to user frustration and lossof productivity.

The small form factor of handheld computing devices requires a carefulbalancing between the displayed graphics and the area provided forreceiving inputs. On the one hand, the small display constrains thedisplay space, which may increase the difficulty of interpreting actionsor results. On the other hand, a virtual keypad or other user interfacescheme is superimposed on or positioned adjacent to an executingapplication, requiring the application to be squeezed into an evensmaller portion of the display.

This balancing act is particularly difficult for single display touchscreen devices. Single display touch screen devices are crippled bytheir limited screen space. When users are entering information into thedevice, through the single display, the ability to interpret informationin the display can be severely hampered, particularly when a complexinteraction between display and interface is required.

SUMMARY

There is a need for a dual multi-display handheld computing device thatprovides for enhanced power and/or versatility compared to conventionalsingle display handheld computing devices. These and other needs areaddressed by the various aspects, embodiments, and/or configurations ofthe present disclosure. Also, while the disclosure is presented in termsof exemplary embodiments, it should be appreciated that individualaspects of the disclosure can be separately claimed.

The multi-display device can execute a phone application that canutilize the multiple screens to provide unique and user-friendly userinterface combinations. Thus, depending on the mode of the phoneapplication, the multi-display device can provide different userinterface configurations. If the configuration of the device changes,the phone application can change its user interface to better adjust tothe new device configuration.

Even further, the disclosure provides techniques directed towardtranslating or otherwise converting content for a multi-display deviceinto content for a single screen device.

The email client user interface provides advantages of providing thebest experience to the user based on various factors. Thus, depending onthe device configuration and the application state, the phoneapplication can adjust. This flexibility allows for conveyinginformation to the user in the most efficient and most easily understoodmanner.

Additionally, it is desirable to have the multi-display device bedockable or otherwise associatable with an additional device. Inaccordance with one exemplary embodiment, the multi-display device isdockable with a smartpad. The exemplary smartpad can include a screen, atouch sensitive display, a configurable area, a gesture captureregion(s), and a camera. The smartpad can also include a port adapted toreceive the multi-display device. The exemplary smartpad is able tocooperate with the multi-display device such that informationdisplayable on the multi-display device is also displayable on thesmartpad. Furthermore, any one or more of the functions on themulti-display device are extendable to the smartpad, with the smartpadcapable of acting as an input/output interface or extension of thesmartpad. Therefore, for example, information from one or more of thedisplays on the multi-display device is displayable on the smartpad.

The phrases “at least one”, “one or more”, and “and/or” are open-endedexpressions that are both conjunctive and disjunctive in operation. Forexample, each of the expressions “at least one of A, B and C”, “at leastone of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B,or C” and “A, B, and/or C” means A alone, B alone, C alone, A and Btogether, A and C together, B and C together, or A, B and C together.

The term “a” or “an” entity refers to one or more of that entity. Assuch, the terms “a” (or “an”), “one or more” and “at least one” can beused interchangeably herein. It is also to be noted that the terms“comprising”, “including”, and “having” can be used interchangeably.

The term “automatic” and variations thereof, as used herein, refers toany process or operation done without material human input when theprocess or operation is performed. However, a process or operation canbe automatic, even though performance of the process or operation usesmaterial or immaterial human input, if the input is received beforeperformance of the process or operation. Human input is deemed to bematerial if such input influences how the process or operation will beperformed. Human input that consents to the performance of the processor operation is not deemed to be “material”.

The term “computer-readable medium” as used herein refers to anytangible storage and/or transmission medium that participate inproviding instructions to a processor for execution. Such a medium maytake many forms, including but not limited to, non-volatile media,volatile media, and transmission media. Non-volatile media includes, forexample, NVRAM, or magnetic or optical disks. Volatile media includesdynamic memory, such as main memory. Common forms of computer-readablemedia include, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, or any other magnetic medium, magneto-optical medium, aCD-ROM, any other optical medium, punch cards, paper tape, any otherphysical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, a solid state medium like a memory card, any other memorychip or cartridge, a carrier wave as described hereinafter, or any othermedium from which a computer can read. A digital file attachment toe-mail or other self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. When the computer-readable media is configured as a database, itis to be understood that the database may be any type of database, suchas relational, hierarchical, object-oriented, and/or the like.Accordingly, the disclosure is considered to include a tangible storagemedium or distribution medium and prior art-recognized equivalents andsuccessor media, in which the software implementations of the presentdisclosure are stored.

The term “desktop” refers to a metaphor used to portray systems. Adesktop is generally considered a “surface” that typically includespictures, called icons, widgets, folders, etc. that can activate showapplications, windows, cabinets, files, folders, documents, and othergraphical items. The icons are generally selectable to initiate a taskthrough user interface interaction to allow a user to executeapplications or conduct other operations.

The term “screen,” “touch screen,” or “touchscreen” refers to a physicalstructure that includes one or more hardware components that provide thedevice with the ability to render a user interface and/or receive userinput. A screen can encompass any combination of gesture capture region,a touch sensitive display, and/or a configurable area. The device canhave one or more physical screens embedded in the hardware. However ascreen may also include an external peripheral device that may beattached and detached from the device. In embodiments, multiple externaldevices may be attached to the device. Thus, in embodiments, the screencan enable the user to interact with the device by touching areas on thescreen and provides information to a user through a display. The touchscreen may sense user contact in a number of different ways, such as bya change in an electrical parameter (e.g., resistance or capacitance),acoustic wave variations, infrared radiation proximity detection, lightvariation detection, and the like. In a resistive touch screen, forexample, normally separated conductive and resistive metallic layers inthe screen pass an electrical current. When a user touches the screen,the two layers make contact in the contacted location, whereby a changein electrical field is noted and the coordinates of the contactedlocation calculated. In a capacitive touch screen, a capacitive layerstores electrical charge, which is discharged to the user upon contactwith the touch screen, causing a decrease in the charge of thecapacitive layer. The decrease is measured, and the contacted locationcoordinates determined. In a surface acoustic wave touch screen, anacoustic wave is transmitted through the screen, and the acoustic waveis disturbed by user contact. A receiving transducer detects the usercontact instance and determines the contacted location coordinates.

The term “display” refers to a portion of one or more screens used todisplay the output of a computer to a user. A display may be asingle-screen display or a multi-screen display, referred to as acomposite display. A composite display can encompass the touch sensitivedisplay of one or more screens. A single physical screen can includemultiple displays that are managed as separate logical displays. Thus,different content can be displayed on the separate displays althoughpart of the same physical screen.

The term “displayed image” refers to an image produced on the display. Atypical displayed image is a window or desktop. The displayed image mayoccupy all or a portion of the display.

The term “display orientation” refers to the way in which a rectangulardisplay is oriented by a user for viewing. The two most common types ofdisplay orientation are portrait and landscape. In landscape mode, thedisplay is oriented such that the width of the display is greater thanthe height of the display (such as a 4:3 ratio, which is 4 units wideand 3 units tall, or a 16:9 ratio, which is 16 units wide and 9 unitstall). Stated differently, the longer dimension of the display isoriented substantially horizontal in landscape mode while the shorterdimension of the display is oriented substantially vertical. In theportrait mode, by contrast, the display is oriented such that the widthof the display is less than the height of the display. Stateddifferently, the shorter dimension of the display is orientedsubstantially horizontal in the portrait mode while the longer dimensionof the display is oriented substantially vertical.

The term “composite display” refers to a logical structure that definesa display that can encompass one or more screens. A multi-screen displaycan be associated with a composite display that encompasses all thescreens. The composite display can have different displaycharacteristics based on the various orientations of the device.

The term “gesture” refers to a user action that expresses an intendedidea, action, meaning, result, and/or outcome. The user action caninclude manipulating a device (e.g., opening or closing a device,changing a device orientation, moving a trackball or wheel, etc.),movement of a body part in relation to the device, movement of animplement or tool in relation to the device, audio inputs, etc. Agesture may be made on a device (such as on the screen) or with thedevice to interact with the device.

The term “module” as used herein refers to any known or later developedhardware, software, firmware, artificial intelligence, fuzzy logic, orcombination of hardware and software that is capable of performing thefunctionality associated with that element.

The term “gesture capture” refers to a sense or otherwise a detection ofan instance and/or type of user gesture. The gesture capture can occurin one or more areas of the screen, A gesture region can be on thedisplay, where it may be referred to as a touch sensitive display or offthe display where it may be referred to as a gesture capture area.

A “multi-screen application” or “multiple-display application” refers toan application that is capable of multiple modes. The multi-screenapplication mode can include, but is not limited to, a single screenmode (where the application is displayed on a single screen) or acomposite display mode (where the application is displayed on two ormore screens). A multi-screen application can have different layoutsoptimized for the mode. Thus, the multi-screen application can havedifferent layouts for a single screen or for a composite display thatcan encompass two or more screens. The different layouts may havedifferent screen/display dimensions and/or configurations on which theuser interfaces of the multi-screen applications can be rendered. Thedifferent layouts allow the application to optimize the application'suser interface for the type of display, e.g., single screen or multiplescreens. In single screen mode, the multi-screen application may presentone window pane of information. In a composite display mode, themulti-screen application may present multiple window panes ofinformation or may provide a larger and a richer presentation becausethere is more space for the display contents. The multi-screenapplications may be designed to adapt dynamically to changes in thedevice and the mode depending on which display (single or composite) thesystem assigns to the multi-screen application. In alternativeembodiments, the user can use a gesture to request the applicationtransition to a different mode, and, if a display is available for therequested mode, the device can allow the application to move to thatdisplay and transition modes.

A “single-screen application” refers to an application that is capableof single screen mode. Thus, the single-screen application can produceonly one window and may not be capable of different modes or differentdisplay dimensions. A single-screen application may not be capable ofthe several modes discussed with the multi-screen application.

The term “window” refers to a, typically rectangular, displayed image onat least part of a display that contains or provides content differentfrom the rest of the screen. The window may obscure the desktop.

The terms “determine”, “calculate” and “compute,” and variationsthereof, as used herein, are used interchangeably and include any typeof methodology, process, mathematical operation or technique.

It shall be understood that the term “means” as used herein shall begiven its broadest possible interpretation in accordance with 35 U.S.C.,Section 112, Paragraph 6. Accordingly, a claim incorporating the term“means” shall cover all structures, materials, or acts set forth herein,and all of the equivalents thereof. Further, the structures, materialsor acts and the equivalents thereof shall include all those described inthe summary of the invention, brief description of the drawings,detailed description, abstract, and claims themselves.

The preceding is a simplified summary of the disclosure to provide anunderstanding of some aspects of the disclosure. This summary is neitheran extensive nor exhaustive overview of the disclosure and its variousaspects, embodiments, and/or configurations. It is intended neither toidentify key or critical elements of the disclosure nor to delineate thescope of the disclosure but to present selected concepts of thedisclosure in a simplified form as an introduction to the more detaileddescription presented below. As will be appreciated, other aspects,embodiments, and/or configurations of the disclosure are possibleutilizing, alone or in combination, one or more of the features setforth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A includes a first view of an embodiment of a multi-screen userdevice;

FIG. 1B includes a second view of an embodiment of a multi-screen userdevice;

FIG. 1C includes a third view of an embodiment of a multi-screen userdevice;

FIG. 1D includes a fourth view of an embodiment of a multi-screen userdevice;

FIG. 1E includes a fifth view of an embodiment of a multi-screen userdevice;

FIG. 1F includes a sixth view of an embodiment of a multi-screen userdevice;

FIG. 1G includes a seventh view of an embodiment of a multi-screen userdevice;

FIG. 1H includes a eighth view of an embodiment of a multi-screen userdevice;

FIG. 1I includes a ninth view of an embodiment of a multi-screen userdevice;

FIG. 1J includes a tenth view of an embodiment of a multi-screen userdevice;

FIG. 2 is a block diagram of an embodiment of the hardware of thedevice;

FIG. 3A is a block diagram of an embodiment of the state model for thedevice based on the device's orientation and/or configuration;

FIG. 3B is a table of an embodiment of the state model for the devicebased on the device's orientation and/or configuration;

FIG. 4A is a first representation of an embodiment of user gesturereceived at a device;

FIG. 4B is a second representation of an embodiment of user gesturereceived at a device;

FIG. 4C is a third representation of an embodiment of user gesturereceived at a device;

FIG. 4D is a fourth representation of an embodiment of user gesturereceived at a device;

FIG. 4E is a fifth representation of an embodiment of user gesturereceived at a device;

FIG. 4F is a sixth representation of an embodiment of user gesturereceived at a device;

FIG. 4G is a seventh representation of an embodiment of user gesturereceived at a device;

FIG. 4H is a eighth representation of an embodiment of user gesturereceived at a device;

FIG. 5A is a block diagram of an embodiment of the device softwareand/or firmware;

FIG. 5B is a second block diagram of an embodiment of the devicesoftware and/or firmware;

FIG. 6A is a first representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6B is a second representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6C is a third representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6D is a fourth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6E is a fifth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6F is a sixth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6G is a seventh representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6H is a eighth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6I is a ninth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6J is a tenth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 7A is representation of a logical window stack;

FIG. 7B is another representation of an embodiment of a logical windowstack;

FIG. 7C is another representation of an embodiment of a logical windowstack;

FIG. 7D is another representation of an embodiment of a logical windowstack;

FIG. 7E is another representation of an embodiment of a logical windowstack;

FIG. 8 is block diagram of an embodiment of a logical data structure fora window stack;

FIG. 9 is a flow chart of an embodiment of a method for creating awindow stack;

FIG. 10 illustrates an exemplary smartpad (SP);

FIG. 11 illustrates an exemplary method of associating the smartpad withthe device;

FIG. 12 illustrates a docked device with the smartpad;

FIGS. 13A-13B illustrate an exemplary method for screen orientation;

FIG. 14 illustrates a method for displaying an application when the SPis in a portrait mode;

FIG. 15 illustrates a method for displaying an application when the SPis in a landscape mode;

FIG. 16 illustrates an example of a dual screen application in portraitmax mode;

FIG. 17 illustrates an example of a dual screen application in max modelandscape;

FIG. 18 illustrates an example of keyboard management on the SP;

FIG. 19 illustrates an example of keyboard management on the SP with anapplication area in max mode;

FIG. 20 illustrates another example of keyboard management for the SP inlandscape mode;

FIG. 21 illustrates an example of a dual screen application running in adual screen emulation mode on the SP with a virtual keyboard;

FIG. 22 illustrates an example of application window stack management onthe SP;

FIG. 23 illustrates another example of application window stackmanagement on the SP;

FIG. 24 illustrates an example of multi application mode of the SP,wherein in the multi application mode the SP emulates the device in itsmini-tablet form;

FIG. 25 illustrates another example of multi application mode of the SP;

FIG. 26 illustrates another example of multi application mode of the SP;

FIG. 27 illustrates another example of multi application mode of the SP;

FIG. 28 illustrates a method for managing screen display;

FIG. 29 illustrates an exemplary method for managing screen display withthe desktop;

FIG. 30 illustrates an exemplary method of managing screen display witha keyboard;

FIGS. 31A and 31B illustrate desktop management on the SP;

FIGS. 32A and 32 B illustrate exemplary methods for desktop panelmanagement;

FIG. 33 illustrates exemplary notification management on the SP;

FIGS. 34A and 34B illustrate exemplary techniques for applicationmanagement;

FIGS. 35A and 35B illustrate an exemplary method for providing desktoppreviews or hints;

FIG. 36 illustrates an exemplary carousel application window stack;

FIG. 37 illustrates an exemplary carousel application window stack witha virtual keyboard;

FIG. 38 illustrates an exemplary method for associating the device andthe SP;

FIG. 39 illustrates an exemplary method for application reorientationbased on SP orientation;

FIG. 40 illustrates an exemplary method for managing the keyboard on theSP;

FIG. 41 illustrates an exemplary method for window manipulation based onone or more gestures;

FIG. 42 illustrates an exemplary method for application highlightingwhen an application is in focus in multi application mode;

FIG. 43 illustrates an exemplary method for application maximization;

FIG. 44 illustrates an exemplary method for transitioning from anapplication window to the desktop;

FIG. 45 illustrates an exemplary method for managing the display of thedesktop and/or one or more panels on the SP;

FIG. 46 illustrates an exemplary method for merging panels for displayon the SP;

FIG. 47 illustrates an exemplary method for previewing one or morepanels on the SP;

FIG. 48 illustrates an exemplary method for stack management in multiapplication mode;

FIG. 49 illustrates an exemplary method for managing the display ofphone application based on application mode and device configuration;

FIG. 50 illustrates an exemplary user interface for a phone application;

FIG. 51 illustrates an exemplary diagram of the possible applicationmodes for a phone application;

FIG. 52A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 52B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 52C illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 52D illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 52E illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 52F illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 53A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 53B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 53C illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 53D illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 53E illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 53F illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 53G illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 53H illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 54A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 54B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 54C illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 54D illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 54E illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 54F illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 55A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 55B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 55C illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 55D illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 55E illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 55F illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 56A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 56B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 56C illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 56D illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 56E illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 56F illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 57A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 57B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 57C illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 57D illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 57E illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 57F illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 58A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 58B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 59A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 59B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 60A illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 60B illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 60C illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 60D illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 60E illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 60F illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 60G illustrates an exemplary user interface for a mode of the phoneapplication;

FIG. 60H illustrates an exemplary user interface for a mode of the phoneapplication.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a letter thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference label.

DETAILED DESCRIPTION

Presented herein are embodiments of a device. The device can be acommunications device, such as a cellular telephone, or other smartdevice. The device can include two screens that are oriented to provideseveral unique display configurations. Further, the device can receiveuser input in unique ways. The overall design and functionality of thedevice provides for an enhanced user experience making the device moreuseful and more efficient.

Mechanical Features:

FIGS. 1A-1J illustrate a device 100 in accordance with embodiments ofthe present disclosure. As described in greater detail below, device 100can be positioned in a number of different ways each of which providesdifferent functionality to a user. The device 100 is a multi-screendevice that includes a primary screen 104 and a secondary screen 108,both of which are touch sensitive. In embodiments, the entire frontsurface of screens 104 and 108 may be touch sensitive and capable ofreceiving input by a user touching the front surface of the screens 104and 108. Primary screen 104 includes touch sensitive display 110, which,in addition to being touch sensitive, also displays information to auser. Secondary screen 108 includes touch sensitive display 114, whichalso displays information to a user. In other embodiments, screens 104and 108 may include more than one display area.

Primary screen 104 also includes a configurable area 112 that has beenconfigured for specific inputs when the user touches portions of theconfigurable area 112. Secondary screen 108 also includes a configurablearea 116 that has been configured for specific inputs. Areas 112 a and116 a have been configured to receive a “back” input indicating that auser would like to view information previously displayed. Areas 112 band 116 b have been configured to receive a “menu” input indicating thatthe user would like to view options from a menu. Areas 112 c and 116 chave been configured to receive a “home” input indicating that the userwould like to view information associated with a “home” view. In otherembodiments, areas 112 a-c and 116 a-c may be configured, in addition tothe configurations described above, for other types of specific inputsincluding controlling features of device 100, some non-limiting examplesincluding adjusting overall system power, adjusting the volume,adjusting the brightness, adjusting the vibration, selecting ofdisplayed items (on either of screen 104 or 108), operating a camera,operating a microphone, and initiating/terminating of telephone calls.Also, in some embodiments, areas 112 a-c and 116 a-c may be configuredfor specific inputs depending upon the application running on device 100and/or information displayed on touch sensitive displays 110 and/or 114.

In addition to touch sensing, primary screen 104 and secondary screen108 may also include areas that receive input from a user withoutrequiring the user to touch the display area of the screen. For example,primary screen 104 includes gesture capture area 120, and secondaryscreen 108 includes gesture capture area 124. These areas are able toreceive input by recognizing gestures made by a user without the needfor the user to actually touch the surface of the display area. Incomparison to touch sensitive displays 110 and 114, the gesture captureareas 120 and 124 are commonly not capable of rendering a displayedimage.

The two screens 104 and 108 are connected together with a hinge 128,shown clearly in FIG. 1C (illustrating a back view of device 100). Hinge128, in the embodiment shown in FIGS. 1A-1J, is a center hinge thatconnects screens 104 and 108 so that when the hinge is closed, screens104 and 108 are juxtaposed (i.e., side-by-side) as shown in FIG. 1B(illustrating a front view of device 100). Hinge 128 can be opened toposition the two screens 104 and 108 in different relative positions toeach other. As described in greater detail below, the device 100 mayhave different functionalities depending on the relative positions ofscreens 104 and 108.

FIG. 1D illustrates the right side of device 100. As shown in FIG. 1D,secondary screen 108 also includes a card slot 132 and a port 136 on itsside. Card slot 132 in embodiments, accommodates different types ofcards including a subscriber identity module (SIM). Port 136 inembodiments is an input/output port (I/O port) that allows device 100 tobe connected to other peripheral devices, such as a display, keyboard,or printing device. As can be appreciated, these are merely someexamples and in other embodiments device 100 may include other slots andports such as slots and ports for accommodating additional memorydevices and/or for connecting other peripheral devices. Also shown inFIG. 1D is an audio jack 140 that accommodates a tip, ring, sleeve (TRS)connector for example to allow a user to utilize headphones or aheadset.

Device 100 also includes a number of buttons 158. For example, FIG. 1Eillustrates the left side of device 100. As shown in FIG. 1E, the sideof primary screen 104 includes three buttons 144, 148, and 152, whichcan be configured for specific inputs. For example, buttons 144, 148,and 152 may be configured to, in combination or alone, control a numberof aspects of device 100. Some non-limiting examples include overallsystem power, volume, brightness, vibration, selection of displayeditems (on either of screen 104 or 108), a camera, a microphone, andinitiation/termination of telephone calls. In some embodiments, insteadof separate buttons two buttons may be combined into a rocker button.This arrangement is useful in situations where the buttons areconfigured to control features such as volume or brightness. In additionto buttons 144, 148, and 152, device 100 also includes a button 156,shown in FIG. 1F, which illustrates the top of device 100. In oneembodiment, button 156 is configured as an on/off button used to controloverall system power to device 100. In other embodiments, button 156 isconfigured to, in addition to or in lieu of controlling system power,control other aspects of device 100. In some embodiments, one or more ofthe buttons 144, 148, 152, and 156 are capable of supporting differentuser commands. By way of example, a normal press has a duration commonlyof less than about 1 second and resembles a quick tap. A medium presshas a duration commonly of 1 second or more but less than about 12seconds. A long press has a duration commonly of about 12 seconds ormore. The function of the buttons is normally specific to theapplication that is currently in focus on the respective display 110 and114. In a telephone application for instance and depending on theparticular button, a normal, medium, or long press can mean end call,increase in call volume, decrease in call volume, and toggle microphonemute. In a camera or video application for instance and depending on theparticular button, a normal, medium, or long press can mean increasezoom, decrease zoom, and take photograph or record video.

There are also a number of hardware components within device 100. Asillustrated in FIG. 1C, device 100 includes a speaker 160 and amicrophone 164. Device 100 also includes a camera 168 (FIG. 1B).Additionally, device 100 includes two position sensors 172A and 172B,which are used to determine the relative positions of screens 104 and108. In one embodiment, position sensors 172A and 172B are Hall effectsensors. However, in other embodiments other sensors can be used inaddition to or in lieu of the Hall effect sensors. An accelerometer 176may also be included as part of device 100 to determine the orientationof the device 100 and/or the orientation of screens 104 and 108.Additional internal hardware components that may be included in device100 are described below with respect to FIG. 2.

The overall design of device 100 allows it to provide additionalfunctionality not available in other communication devices. Some of thefunctionality is based on the various positions and orientations thatdevice 100 can have. As shown in FIGS. 1B-1G, device 100 can be operatedin an “open” position where screens 104 and 108 are juxtaposed. Thisposition allows a large display area for displaying information to auser. When position sensors 172A and 172B determine that device 100 isin the open position, they can generate a signal that can be used totrigger different events such as displaying information on both screens104 and 108. Additional events may be triggered if accelerometer 176determines that device 100 is in a portrait position (FIG. 1B) asopposed to a landscape position (not shown).

In addition to the open position, device 100 may also have a “closed”position illustrated in FIG. 1H. Again, position sensors 172A and 172Bcan generate a signal indicating that device 100 is in the “closed”position. This can trigger an event that results in a change ofdisplayed information on screen 104 and/or 108. For example, device 100may be programmed to stop displaying information on one of the screens,e.g., screen 108, since a user can only view one screen at a time whendevice 100 is in the “closed” position. In other embodiments, the signalgenerated by position sensors 172A and 172B, indicating that the device100 is in the “closed” position, can trigger device 100 to answer anincoming telephone call. The “closed” position can also be a preferredposition for utilizing the device 100 as a mobile phone.

Device 100 can also be used in an “easel” position which is illustratedin FIG. 1I. In the “easel” position, screens 104 and 108 are angled withrespect to each other and facing outward with the edges of screens 104and 108 substantially horizontal. In this position, device 100 can beconfigured to display information on both screens 104 and 108 to allowtwo users to simultaneously interact with device 100. When device 100 isin the “easel” position, sensors 172A and 172B generate a signalindicating that the screens 104 and 108 are positioned at an angle toeach other, and the accelerometer 176 can generate a signal indicatingthat device 100 has been placed so that the edge of screens 104 and 108are substantially horizontal. The signals can then be used incombination to generate events that trigger changes in the display ofinformation on screens 104 and 108.

FIG. 1J illustrates device 100 in a “modified easel” position. In the“modified easel” position, one of screens 104 or 108 is used as a standand is faced down on the surface of an object such as a table. Thisposition provides a convenient way for information to be displayed to auser in landscape orientation. Similar to the easel position, whendevice 100 is in the “modified easel” position, position sensors 172Aand 172B generate a signal indicating that the screens 104 and 108 arepositioned at an angle to each other. The accelerometer 176 wouldgenerate a signal indicating that device 100 has been positioned so thatone of screens 104 and 108 is faced downwardly and is substantiallyhorizontal. The signals can then be used to generate events that triggerchanges in the display of information of screens 104 and 108. Forexample, information may not be displayed on the screen that is facedown since a user cannot see the screen.

Transitional states are also possible. When the position sensors 172Aand B and/or accelerometer indicate that the screens are being closed orfolded (from open), a closing transitional state is recognized.Conversely when the position sensors 172A and B indicate that thescreens are being opened or folded (from closed), an openingtransitional state is recognized. The closing and opening transitionalstates are typically time-based, or have a maximum time duration from asensed starting point. Normally, no user input is possible when one ofthe closing and opening states is in effect. In this manner, incidentaluser contact with a screen during the closing or opening function is notmisinterpreted as user input. In embodiments, another transitional stateis possible when the device 100 is closed. This additional transitionalstate allows the display to switch from one screen 104 to the secondscreen 108 when the device 100 is closed based on some user input, e.g.,a double tap on the screen 110,114.

As can be appreciated, the description of device 100 is made forillustrative purposes only, and the embodiments are not limited to thespecific mechanical features shown in FIGS. 1A-1J and described above.In other embodiments, device 100 may include additional features,including one or more additional buttons, slots, display areas, hinges,and/or locking mechanisms. Additionally, in embodiments, the featuresdescribed above may be located in different parts of device 100 andstill provide similar functionality. Therefore, FIGS. 1A-1J and thedescription provided above are nonlimiting.

Hardware Features:

FIG. 2 illustrates components of a device 100 in accordance withembodiments of the present disclosure. In general, the device 100includes a primary screen 104 and a secondary screen 108. While theprimary screen 104 and its components are normally enabled in both theopened and closed positions or states, the secondary screen 108 and itscomponents are normally enabled in the opened state but disabled in theclosed state. However, even when in the closed state a user orapplication triggered interrupt (such as in response to a phoneapplication or camera application operation) can flip the active screen,or disable the primary screen 104 and enable the secondary screen 108,by a suitable command. Each screen 104, 108 can be touch sensitive andcan include different operative areas. For example, a first operativearea, within each touch sensitive screen 104 and 108, may comprise atouch sensitive display 110, 114. In general, the touch sensitivedisplay 110, 114 may comprise a full color, touch sensitive display. Asecond area within each touch sensitive screen 104 and 108 may comprisea gesture capture region 120, 124. The gesture capture region 120, 124may comprise an area or region that is outside of the touch sensitivedisplay 110, 114 area, and that is capable of receiving input, forexample in the form of gestures provided by a user. However, the gesturecapture region 120, 124 does not include pixels that can perform adisplay function or capability.

A third region of the touch sensitive screens 104 and 108 may comprise aconfigurable area 112, 116. The configurable area 112, 116 is capable ofreceiving input and has display or limited display capabilities. Inembodiments, the configurable area 112, 116 may present different inputoptions to the user. For example, the configurable area 112, 116 maydisplay buttons or other relatable items. Moreover, the identity ofdisplayed buttons, or whether any buttons are displayed at all withinthe configurable area 112, 116 of a touch sensitive screen 104 or 108,may be determined from the context in which the device 100 is usedand/or operated. In an exemplary embodiment, the touch sensitive screens104 and 108 comprise liquid crystal display devices extending across atleast those regions of the touch sensitive screens 104 and 108 that arecapable of providing visual output to a user, and a capacitive inputmatrix over those regions of the touch sensitive screens 104 and 108that are capable of receiving input from the user.

One or more display controllers 216 a, 216 b may be provided forcontrolling the operation of the touch sensitive screens 104 and 108,including input (touch sensing) and output (display) functions. In theexemplary embodiment illustrated in FIG. 2, a separate touch screencontroller 216 a or 216 b is provided for each touch screen 104 and 108.In accordance with alternate embodiments, a common or shared touchscreen controller may be used to control each of the included touchsensitive screens 104 and 108. In accordance with still otherembodiments, the functions of a touch screen controller may beincorporated into other components, such as a processor 204.

The processor 204 may comprise a general purpose programmable processoror controller for executing application programming or instructions. Inaccordance with at least some embodiments, the processor 204 may includemultiple processor cores, and/or implement multiple virtual processors.In accordance with still other embodiments, the processor 204 mayinclude multiple physical processors. As a particular example, theprocessor 204 may comprise a specially configured application specificintegrated circuit (ASIC) or other integrated circuit, a digital signalprocessor, a controller, a hardwired electronic or logic circuit, aprogrammable logic device or gate array, a special purpose computer, orthe like. The processor 204 generally functions to run programming codeor instructions implementing various functions of the device 100.

A communication device 100 may also include memory 208 for use inconnection with the execution of application programming or instructionsby the processor 204, and for the temporary or long term storage ofprogram instructions and/or data. As examples, the memory 208 maycomprise RAM, DRAM, SDRAM, or other solid state memory. Alternatively orin addition, data storage 212 may be provided. Like the memory 208, thedata storage 212 may comprise a solid state memory device or devices.Alternatively or in addition, the data storage 212 may comprise a harddisk drive or other random access memory.

In support of communications functions or capabilities, the device 100can include a cellular telephony module 228. As examples, the cellulartelephony module 228 can comprise a GSM, CDMA, FDMA and/or analogcellular telephony transceiver capable of supporting voice, multimediaand/or data transfers over a cellular network. Alternatively or inaddition, the device 100 can include an additional or other wirelesscommunications module 232. As examples, the other wirelesscommunications module 232 can comprise a Wi-Fi, BLUETOOTH™, WiMax,infrared, or other wireless communications link. The cellular telephonymodule 228 and the other wireless communications module 232 can each beassociated with a shared or a dedicated antenna 224.

A port interface 252 may be included. The port interface 252 may includeproprietary or universal ports to support the interconnection of thedevice 100 to other devices or components, such as a dock, which may ormay not include additional or different capabilities from those integralto the device 100. In addition to supporting an exchange ofcommunication signals between the device 100 and another device orcomponent, the docking port 136 and/or port interface 252 can supportthe supply of power to or from the device 100. The port interface 252also comprises an intelligent element that comprises a docking modulefor controlling communications or other interactions between the device100 and a connected device or component.

An input/output module 248 and associated ports may be included tosupport communications over wired networks or links, for example withother communication devices, server devices, and/or peripheral devices.Examples of an input/output module 248 include an Ethernet port, aUniversal Serial Bus (USB) port, Institute of Electrical and ElectronicsEngineers (IEEE) 1394, or other interface.

An audio input/output interface/device(s) 244 can be included to provideanalog audio to an interconnected speaker or other device, and toreceive analog audio input from a connected microphone or other device.As an example, the audio input/output interface/device(s) 244 maycomprise an associated amplifier and analog to digital converter.Alternatively or in addition, the device 100 can include an integratedaudio input/output device 256 and/or an audio jack for interconnectingan external speaker or microphone. For example, an integrated speakerand an integrated microphone can be provided, to support near talk orspeaker phone operations.

Hardware buttons 158 can be included for example for use in connectionwith certain control operations. Examples include a master power switch,volume control, etc., as described in conjunction with FIGS. 1A through1J. One or more image capture interfaces/devices 240, such as a camera,can be included for capturing still and/or video images. Alternativelyor in addition, an image capture interface/device 240 can include ascanner or code reader. An image capture interface/device 240 caninclude or be associated with additional elements, such as a flash orother light source.

The device 100 can also include a global positioning system (GPS)receiver 236. In accordance with embodiments of the present invention,the GPS receiver 236 may further comprise a GPS module that is capableof providing absolute location information to other components of thedevice 100. An accelerometer(s) 176 may also be included. For example,in connection with the display of information to a user and/or otherfunctions, a signal from the accelerometer 176 can be used to determinean orientation and/or format in which to display that information to theuser.

Embodiments of the present invention can also include one or moreposition sensor(s) 172. The position sensor 172 can provide a signalindicating the position of the touch sensitive screens 104 and 108relative to one another. This information can be provided as an input,for example to a user interface application, to determine an operatingmode, characteristics of the touch sensitive displays 110, 114, and/orother device 100 operations. As examples, a screen position sensor 172can comprise a series of Hall effect sensors, a multiple positionswitch, an optical switch, a Wheatstone bridge, a potentiometer, orother arrangement capable of providing a signal indicating of multiplerelative positions the touch screens are in.

Communications between various components of the device 100 can becarried by one or more buses 222. In addition, power can be supplied tothe components of the device 100 from a power source and/or powercontrol module 260. The power control module 260 can, for example,include a battery, an AC to DC converter, power control logic, and/orports for interconnecting the device 100 to an external source of power.

Device State:

FIGS. 3A and 3B represent illustrative states of device 100. While anumber of illustrative states are shown, and transitions from a firststate to a second state, it is to be appreciated that the illustrativestate diagram may not encompass all possible states and/or all possibletransitions from a first state to a second state. As illustrated in FIG.3, the various arrows between the states (illustrated by the staterepresented in the circle) represent a physical change that occurs tothe device 100, that is detected by one or more of hardware andsoftware, the detection triggering one or more of a hardware and/orsoftware interrupt that is used to control and/or manage one or morefunctions of device 100.

As illustrated in FIG. 3A, there are twelve exemplary “physical” states:closed 304, transition 308 (or opening transitional state), easel 312,modified easel 316, open 320, inbound/outbound call or communication324, image/video capture 328, transition 332 (or closing transitionalstate), landscape 340, docked 336, docked 344 and landscape 348. Next toeach illustrative state is a representation of the physical state of thedevice 100 with the exception of states 324 and 328, where the state isgenerally symbolized by the international icon for a telephone and theicon for a camera, respectfully.

In state 304, the device is in a closed state with the device 100generally oriented in the portrait direction with the primary screen 104and the secondary screen 108 back-to-back in different planes (see FIG.1H). From the closed state, the device 100 can enter, for example,docked state 336, where the device 100 is coupled with a dockingstation, docking cable, or in general docked or associated with one ormore other devices or peripherals, or the landscape state 340, where thedevice 100 is generally oriented with the primary screen 104 facing theuser, and the primary screen 104 and the secondary screen 108 beingback-to-back.

In the closed state, the device can also move to a transitional statewhere the device remains closed but the display is moved from one screen104 to another screen 108 based on a user input, e.g., a double tap onthe screen 110, 114. Still another embodiment includes a bilateralstate. In the bilateral state, the device remains closed, but a singleapplication displays at least one window on both the first display 110and the second display 114. The windows shown on the first and seconddisplay 110, 114 may be the same or different based on the applicationand the state of that application. For example, while acquiring an imagewith a camera, the device may display the view finder on the firstdisplay 110 and displays a preview for the photo subjects (full screenand mirrored left-to-right) on the second display 114.

In state 308, a transition state from the closed state 304 to thesemi-open state or easel state 312, the device 100 is shown opening withthe primary screen 104 and the secondary screen 108 being rotated arounda point of axis coincidence with the hinge. Upon entering the easelstate 312, the primary screen 104 and the secondary screen 108 areseparated from one another such that, for example, the device 100 cansit in an easel-like configuration on a surface.

In state 316, known as the modified easel position, the device 100 hasthe primary screen 104 and the secondary screen 108 in a similarrelative relationship to one another as in the easel state 312, with thedifference being one of the primary screen 104 or the secondary screen108 are placed on a surface as shown.

State 320 is the open state where the primary screen 104 and thesecondary screen 108 are generally on the same plane. From the openstate, the device 100 can transition to the docked state 344 or the openlandscape state 348. In the open state 320, the primary screen 104 andthe secondary screen 108 are generally in the portrait-like orientationwhile in landscaped state 348 the primary screen 104 and the secondaryscreen 108 are generally in a landscape-like orientation.

State 324 is illustrative of a communication state, such as when aninbound or outbound call is being received or placed, respectively, bythe device 100. While not illustrated for clarity, it should beappreciated the device 100 can transition to the inbound/outbound callstate 324 from any state illustrated in FIG. 3. In a similar manner, theimage/video capture state 328 can be entered into from any other statein FIG. 3, with the image/video capture state 328 allowing the device100 to take one or more images via a camera and/or videos with a videocapture device 240.

Transition state 332 illustratively shows primary screen 104 and thesecondary screen 108 being closed upon one another for entry into, forexample, the closed state 304.

FIG. 3B illustrates, with reference to the key, the inputs that arereceived to detect a transition from a first state to a second state. InFIG. 3B, various combinations of states are shown with in general, aportion of the columns being directed toward a portrait state 352, alandscape state 356, and a portion of the rows being directed toportrait state 360 and landscape state 364.

In FIG. 3B, the Key indicates that “H” represents an input from one ormore Hall Effect sensors, “A” represents an input from one or moreaccelerometers, “T” represents an input from a timer, “P” represents acommunications trigger input and “I” represents an image and/or videocapture request input. Thus, in the center portion 376 of the chart, aninput, or combination of inputs, are shown that represent how the device100 detects a transition from a first physical state to a secondphysical state.

As discussed, in the center portion of the chart 376, the inputs thatare received enable the detection of a transition from, for example, aportrait open state to a landscape easel state—shown in bold—“HAT.” Forthis exemplary transition from the portrait open to the landscape easelstate, a Hall Effect sensor (“H”), an accelerometer (“A”) and a timer(“T”) input may be needed. The timer input can be derived from, forexample, a clock associated with the processor.

In addition to the portrait and landscape states, a docked state 368 isalso shown that is triggered based on the receipt of a docking signal372. As discussed above and in relation to FIG. 3, the docking signalcan be triggered by the association of the device 100 with one or moreother device 100s, accessories, peripherals, smart docks, or the like.

User Interaction:

FIGS. 4A through 4H depict various graphical representations of gestureinputs that may be recognized by the screens 104, 108. The gestures maybe performed not only by a user's body part, such as a digit, but alsoby other devices, such as a stylus, that may be sensed by the contactsensing portion(s) of a screen 104, 108. In general, gestures areinterpreted differently, based on where the gestures are performed(either directly on the display 110, 114 or in the gesture captureregion 120, 124). For example, gestures in the display 110,114 may bedirected to a desktop or application, and gestures in the gesturecapture region 120, 124 may be interpreted as for the system.

With reference to FIGS. 4A-4H, a first type of gesture, a touch gesture420, is substantially stationary on the screen 104,108 for a selectedlength of time. A circle 428 represents a touch or other contact typereceived at particular location of a contact sensing portion of thescreen. The circle 428 may include a border 432, the thickness of whichindicates a length of time that the contact is held substantiallystationary at the contact location. For instance, a tap 420 (or shortpress) has a thinner border 432 a than the border 432 b for a long press424 (or for a normal press). The long press 424 may involve a contactthat remains substantially stationary on the screen for longer timeperiod than that of a tap 420. As will be appreciated, differentlydefined gestures may be registered depending upon the length of timethat the touch remains stationary prior to contact cessation or movementon the screen.

With reference to FIG. 4C, a drag gesture 400 on the screen 104,108 isan initial contact (represented by circle 428) with contact movement 436in a selected direction. The initial contact 428 may remain stationaryon the screen 104,108 for a certain amount of time represented by theborder 432. The drag gesture typically requires the user to contact anicon, window, or other displayed image at a first location followed bymovement of the contact in a drag direction to a new second locationdesired for the selected displayed image. The contact movement need notbe in a straight line but have any path of movement so long as thecontact is substantially continuous from the first to the secondlocations.

With reference to FIG. 4D, a flick gesture 404 on the screen 104,108 isan initial contact (represented by circle 428) with truncated contactmovement 436 (relative to a drag gesture) in a selected direction. Inembodiments, a flick has a higher exit velocity for the last movement inthe gesture compared to the drag gesture. The flick gesture can, forinstance, be a finger snap following initial contact. Compared to a draggesture, a flick gesture generally does not require continual contactwith the screen 104,108 from the first location of a displayed image toa predetermined second location. The contacted displayed image is movedby the flick gesture in the direction of the flick gesture to thepredetermined second location. Although both gestures commonly can movea displayed image from a first location to a second location, thetemporal duration and distance of travel of the contact on the screen isgenerally less for a flick than for a drag gesture.

With reference to FIG. 4E, a pinch gesture 408 on the screen 104,108 isdepicted. The pinch gesture 408 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104 or 108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in opposing directions. Stated anotherway, the first contact movement 436 a is towards the second contact 436b, and the second contact movement 436 b is towards the first contact436 a. More simply stated, the pinch gesture 408 may be accomplished bya user's digits touching the screen 104,108 in a pinching motion.

With reference to FIG. 4F, a spread gesture 410 on the screen 104,108 isdepicted. The spread gesture 410 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104,108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in a common direction. Stated anotherway, the first and second contact movements 436 a, b are away from thefirst and second contacts 428 a, b. More simply stated, the spreadgesture 410 may be accomplished by a user's digits touching the screen104,108 in a spreading motion.

The above gestures may be combined in any manner, such as those shown byFIGS. 4G and 4H, to produce a determined functional result. For example,in FIG. 4G a tap gesture 420 is combined with a drag or flick gesture412 in a direction away from the tap gesture 420. In FIG. 4H, a tapgesture 420 is combined with a drag or flick gesture 412 in a directiontowards the tap gesture 420.

The functional result of receiving a gesture can vary depending on anumber of factors, including a state of the device 100, display 110,114, or screen 104, 108, a context associated with the gesture, orsensed location of the gesture. The state of the device commonly refersto one or more of a configuration of the device 100, a displayorientation, and user and other inputs received by the device 100.Context commonly refers to one or more of the particular application(s)selected by the gesture and the portion(s) of the application currentlyexecuting, whether the application is a single- or multi-screenapplication, and whether the application is a multi-screen applicationdisplaying one or more windows in one or more screens or in one or morestacks. Sensed location of the gesture commonly refers to whether thesensed set(s) of gesture location coordinates are on a touch sensitivedisplay 110, 114 or a gesture capture region 120, 124, whether thesensed set(s) of gesture location coordinates are associated with acommon or different display or screen 104,108, and/or what portion ofthe gesture capture region contains the sensed set(s) of gesturelocation coordinates.

A tap, when received by an a touch sensitive display 110, 114, can beused, for instance, to select an icon to initiate or terminate executionof a corresponding application, to maximize or minimize a window, toreorder windows in a stack, and to provide user input such as bykeyboard display or other displayed image. A drag, when received by atouch sensitive display 110, 114, can be used, for instance, to relocatean icon or window to a desired location within a display, to reorder astack on a display, or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). A flick, whenreceived by a touch sensitive display 110, 114 or a gesture captureregion 120, 124, can be used to relocate a window from a first displayto a second display or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). Unlike thedrag gesture, however, the flick gesture is generally not used to movethe displayed image to a specific user-selected location but to adefault location that is not configurable by the user.

The pinch gesture, when received by a touch sensitive display 110, 114or a gesture capture region 120, 124, can be used to minimize orotherwise increase the displayed area or size of a window (typicallywhen received entirely by a common display), to switch windows displayedat the top of the stack on each display to the top of the stack of theother display (typically when received by different displays orscreens), or to display an application manager (a “pop-up window” thatdisplays the windows in the stack). The spread gesture, when received bya touch sensitive display 110, 114 or a gesture capture region 120, 124,can be used to maximize or otherwise decrease the displayed area or sizeof a window, to switch windows displayed at the top of the stack on eachdisplay to the top of the stack of the other display (typically whenreceived by different displays or screens), or to display an applicationmanager (typically when received by an off-screen gesture capture regionon the same or different screens).

The combined gestures of FIG. 4G, when received by a common displaycapture region in a common display or screen 104,108, can be used tohold a first window stack location in a first stack constant for adisplay receiving the gesture while reordering a second window stacklocation in a second window stack to include a window in the displayreceiving the gesture. The combined gestures of FIG. 4H, when receivedby different display capture regions in a common display or screen104,108 or in different displays or screens, can be used to hold a firstwindow stack location in a first window stack constant for a displayreceiving the tap part of the gesture while reordering a second windowstack location in a second window stack to include a window in thedisplay receiving the flick or drag gesture. Although specific gesturesand gesture capture regions in the preceding examples have beenassociated with corresponding sets of functional results, it is to beappreciated that these associations can be redefined in any manner toproduce differing associations between gestures and/or gesture captureregions and/or functional results.

Firmware and Software:

The memory 508 may store and the processor 504 may execute one or moresoftware components. These components can include at least one operatingsystem (OS) 516, an application manager 562, a desktop 566, and/or oneor more applications 564 a and/or 564 b from an application store 560.The OS 516 can include a framework 520, one or more frame buffers 548,one or more drivers 512, previously described in conjunction with FIG.2, and/or a kernel 518. The OS 516 can be any software, consisting ofprograms and data, which manages computer hardware resources andprovides common services for the execution of various applications 564.The OS 516 can be any operating system and, at least in someembodiments, dedicated to mobile devices, including, but not limited to,Linux, ANDROID™, iPhone OS (IOS™), WINDOWS PHONE 7™, etc. The OS 516 isoperable to provide functionality to the phone by executing one or moreoperations, as described herein.

The applications 564 can be any higher level software that executesparticular functionality for the user. Applications 564 can includeprograms such as email clients, web browsers, texting applications,games, media players, office suites, etc. The applications 564 can bestored in an application store 560, which may represent any memory ordata storage, and the management software associated therewith, forstoring the applications 564. Once executed, the applications 564 may berun in a different area of memory 508.

The framework 520 may be any software or data that allows the multipletasks running on the device to interact. In embodiments, at leastportions of the framework 520 and the discrete components describedhereinafter may be considered part of the OS 516 or an application 564.However, these portions will be described as part of the framework 520,but those components are not so limited. The framework 520 can include,but is not limited to, a Multi-Display Management (MDM) module 524, aSurface Cache module 528, a Window Management module 532, an InputManagement module 536, a Task Management module 540, an ApplicationModel Manager 542, a Display Controller, one or more frame buffers 548,a task stack 552, one or more window stacks 550 (which is a logicalarrangement of windows and/or desktops in a display area), and/or anevent buffer 556.

The MDM module 524 includes one or more modules that are operable tomanage the display of applications or other data on the screens of thedevice. An embodiment of the MDM module 524 is described in conjunctionwith FIG. 5B. In embodiments, the MDM module 524 receives inputs fromthe other OS 516 components, such as, the drivers 512, and from theapplications 564 to determine continually the state of the device 100.The inputs assist the MDM module 524 in determining how to configure andallocate the displays according to the application's preferences andrequirements, and the user's actions. Once a determination for displayconfigurations is made, the MDM module 524 can bind the applications 564to a display. The configuration may then be provided to one or moreother components to generate a window with a display.

The Surface Cache module 528 includes any memory or storage and thesoftware associated therewith to store or cache one or more images ofwindows. A series of active and/or non-active windows (or other displayobjects, such as, a desktop display) can be associated with eachdisplay. An active window (or other display object) is currentlydisplayed. A non-active windows (or other display objects) were openedand, at some time, displayed but are now not displayed. To enhance theuser experience, before a window transitions from an active state to aninactive state, a “screen shot” of a last generated image of the window(or other display object) can be stored. The Surface Cache module 528may be operable to store a bitmap of the last active image of a window(or other display object) not currently displayed. Thus, the SurfaceCache module 528 stores the images of non-active windows (or otherdisplay objects) in a data store.

In embodiments, the Window Management module 532 is operable to managethe windows (or other display objects) that are active or not active oneach of the displays. The Window Management module 532, based oninformation from the MDM module 524, the OS 516, or other components,determines when a window (or other display object) is visible or notactive. The Window Management module 532 may then put a non-visiblewindow (or other display object) in a “not active state” and, inconjunction with the Task Management module Task Management 540 suspendsthe application's operation. Further, the Window Management module 532may assign, through collaborative interaction with the MDM module 524, adisplay identifier to the window (or other display object) or manage oneor more other items of data associated with the window (or other displayobject). The Window Management module 532 may also provide the storedinformation to the application 564, the Task Management module 540, orother components interacting with or associated with the window (orother display object). The Window Management module 532 can alsoassociate an input task with a window based on window focus and displaycoordinates within the motion space.

The Input Management module 536 is operable to manage events that occurwith the device. An event is any input into the window environment, forexample, a user interface interactions with a user. The Input Managementmodule 536 receives the events and logically stores the events in anevent buffer 556. Events can include such user interface interactions asa “down event,” which occurs when a screen 104, 108 receives a touchsignal from a user, a “move event,” which occurs when the screen 104,108 determines that a user's finger is moving across a screen(s), an “upevent, which occurs when the screen 104, 108 determines that the userhas stopped touching the screen 104, 108, etc. These events arereceived, stored, and forwarded to other modules by the Input Managementmodule 536. The Input Management module 536 may also map screen inputsto a motion space which is the culmination of all physical and virtualdisplay available on the device.

The motion space is a virtualized space that includes all touchsensitive displays 110,114 “tiled” together to mimic the physicaldimensions of the device 100. For example, when the device 100 isunfolded, the motion space size may be 960×800, which may be the numberof pixels in the combined display area for both touch sensitive displays110, 114. If a user touches on a first touch sensitive display 110 onlocation (40, 40), a full screen window can receive touch event withlocation (40, 40). If a user touches on a second touch sensitive display114, with location (40, 40), the full screen window can receive touchevent with location (520, 40), because the second touch sensitivedisplay 114 is on the right side of the first touch sensitive display110, so the device 100 can offset the touch by the first touch sensitivedisplay's 110 width, which is 480 pixels. When a hardware event occurswith location info from a driver 512, the framework 520 can up-scale thephysical location to the motion space because the location of the eventmay be different based on the device orientation and state. The motionspace may be as described in U.S. patent application Ser. No.13/187,026, filed Jul. 20, 2011, entitled “Systems and Methods forReceiving Gesture Inputs Spanning Multiple Input Devices,” which ishereby incorporated by reference in its entirety for all that it teachesand for all purposes.

A task can be an application and a sub-task can be an applicationcomponent that provides a window with which users can interact to dosomething, such as dial the phone, take a photo, send an email, or viewa map. Each task may be given a window in which to draw a userinterface. The window typically fills a display (for example, touchsensitive display 110,114), but may be smaller than the display 110,114and float on top of other windows. An application usually consists ofmultiple sub-tasks that are loosely bound to each other. Typically, onetask in an application is specified as the “main” task, which ispresented to the user when launching the application for the first time.Each task can then start another task or sub-task to perform differentactions.

The Task Management module 540 is operable to manage the operation ofone or more applications 564 that may be executed by the device. Thus,the Task Management module 540 can receive signals to launch, suspend,terminate, etc. an application or application sub-tasks stored in theapplication store 560. The Task Management module 540 may theninstantiate one or more tasks or sub-tasks of the application 564 tobegin operation of the application 564. Further, the Task ManagementModule 540 may launch, suspend, or terminate a task or sub-task as aresult of user input or as a result of a signal from a collaboratingframework 520 component. The Task Management Module 540 is responsiblefor managing the lifecycle of applications (tasks and sub-task) fromwhen the application is launched to when the application is terminated.

The processing of the Task Management Module 540 is facilitated by atask stack 552, which is a logical structure associated with the TaskManagement Module 540. The task stack 552 maintains the state of alltasks and sub-tasks on the device 100. When some component of theoperating system 516 requires a task or sub-task to transition in itslifecycle, the OS 516 component can notify the Task Management Module540. The Task Management Module 540 may then locate the task orsub-task, using identification information, in the task stack 552, andsend a signal to the task or sub-task indicating what kind of lifecycletransition the task needs to execute. Informing the task or sub-task ofthe transition allows the task or sub-task to prepare for the lifecyclestate transition. The Task Management Module 540 can then execute thestate transition for the task or sub-task. In embodiments, the statetransition may entail triggering the OS kernel 518 to terminate the taskwhen termination is required.

Further, the Task Management module 540 may suspend the application 564based on information from the Window Management Module 532. Suspendingthe application 564 may maintain application data in memory but maylimit or stop the application 564 from rendering a window or userinterface. Once the application becomes active again, the TaskManagement module 540 can again trigger the application to render itsuser interface. In embodiments, if a task is suspended, the task maysave the task's state in case the task is terminated. In the suspendedstate, the application task may not receive input because theapplication window is not visible to the user.

The frame buffer 548 is a logical structure(s) used to render the userinterface. The frame buffer 548 can be created and destroyed by the OSkernel 518. However, the Display Controller 544 can write the imagedata, for the visible windows, into the frame buffer 548. A frame buffer548 can be associated with one screen or multiple screens. Theassociation of a frame buffer 548 with a screen can be controlleddynamically by interaction with the OS kernel 518. A composite displaymay be created by associating multiple screens with a single framebuffer 548. Graphical data used to render an application's window userinterface may then be written to the single frame buffer 548, for thecomposite display, which is output to the multiple screens 104,108. TheDisplay Controller 544 can direct an application's user interface to aportion of the frame buffer 548 that is mapped to a particular display110,114, thus, displaying the user interface on only one screen 104 or108. The Display Controller 544 can extend the control over userinterfaces to multiple applications, controlling the user interfaces foras many displays as are associated with a frame buffer 548 or a portionthereof. This approach compensates for the multiple physical screens104,108 that are in use by the software component above the DisplayController 544.

The Application Manager 562 is an application that provides apresentation layer for the window environment. Thus, the ApplicationManager 562 provides the graphical model for rendering by the TaskManagement Module 540. Likewise, the Desktop 566 provides thepresentation layer for the Application Store 560. Thus, the desktopprovides a graphical model of a surface having selectable applicationicons for the Applications 564 in the Application Store 560 that can beprovided to the Window Management Module 556 for rendering.

Further, the framework can include an Application Model Manager (AMM)542. The Application Manager 562 may interface with the AMM 542. Inembodiments, the AMM 542 receives state change information from thedevice 100 regarding the state of applications (which are running orsuspended). The AMM 542 can associate bit map images from the SurfaceCache Module 528 to the tasks that are alive (running or suspended).Further, the AMM 542 can convert the logical window stack maintained inthe Task Manager Module 540 to a linear (“film strip” or “deck ofcards”) organization that the user perceives when the using the offgesture capture area 120 to sort through the windows. Further, the AMM542 may provide a list of executing applications to the ApplicationManager 562.

An embodiment of the MDM module 524 is shown in FIG. 5B. The MDM module524 is operable to determine the state of the environment for thedevice, including, but not limited to, the orientation of the device,whether the device 100 is opened or closed, what applications 564 areexecuting, how the applications 564 are to be displayed, what actionsthe user is conducting, the tasks being displayed, etc. To configure thedisplay, the MDM module 524 interprets these environmental factors anddetermines a display configuration, as described in conjunction withFIGS. 6A-6J. Then, the MDM module 524 can bind the applications 564 orother device components to the displays. The configuration may then besent to the Display Controller 544 and/or the other components withinthe OS 516 to generate the display. The MDM module 524 can include oneor more of, but is not limited to, a Display Configuration Module 568, aPreferences Module 572, a Device State Module 574, a Gesture Module 576,a Requirements Module 580, an Event Module 584, and/or a Binding Module588.

The Display Configuration Module 568 determines the layout for thedisplay. In embodiments, the Display Configuration Module 568 candetermine the environmental factors. The environmental factors may bereceived from one or more other MDM modules 524 or from other sources.The Display Configuration Module 568 can then determine from the list offactors the best configuration for the display. Some embodiments of thepossible configurations and the factors associated therewith aredescribed in conjunction with FIGS. 6A-6F.

The Preferences Module 572 is operable to determine display preferencesfor an application 564 or other component. For example, an applicationcan have a preference for Single or Dual displays. The PreferencesModule 572 can determine an application's display preference (e.g., byinspecting the application's preference settings) and may allow theapplication 564 to change to a mode (e.g., single screen, dual screen,max, etc.) if the device 100 is in a state that can accommodate thepreferred mode. However, some user interface policies may disallow amode even if the mode is available. As the configuration of the devicechanges, the preferences may be reviewed to determine if a betterdisplay configuration can be achieved for an application 564.

The Device State Module 574 is operable to determine or receive thestate of the device. The state of the device can be as described inconjunction with FIGS. 3A and 3B. The state of the device can be used bythe Display Configuration Module 568 to determine the configuration forthe display. As such, the Device State Module 574 may receive inputs andinterpret the state of the device. The state information is thenprovided to the Display Configuration Module 568.

The Gesture Module 576 is shown as part of the MDM module 524, but, inembodiments, the Gesture module 576 may be a separate Framework 520component that is separate from the MDM module 524. In embodiments, theGesture Module 576 is operable to determine if the user is conductingany actions on any part of the user interface. In alternativeembodiments, the Gesture Module 576 receives user interface actions fromthe configurable area 112,116 only. The Gesture Module 576 can receivetouch events that occur on the configurable area 112,116 (or possiblyother user interface areas) by way of the Input Management Module 536and may interpret the touch events (using direction, speed, distance,duration, and various other parameters) to determine what kind ofgesture the user is performing. When a gesture is interpreted, theGesture Module 576 can initiate the processing of the gesture and, bycollaborating with other Framework 520 components, can manage therequired window animation. The Gesture Module 576 collaborates with theApplication Model Manager 542 to collect state information with respectto which applications are running (active or paused) and the order inwhich applications must appear when a user gesture is performed. TheGesture Module 576 may also receive references to bitmaps (from theSurface Cache Module 528) and live windows so that when a gesture occursit can instruct the Display Controller 544 how to move the window(s)across the display 110,114. Thus, suspended applications may appear tobe running when those windows are moved across the display 110,114.

Further, the Gesture Module 576 can receive task information either fromthe Task Manage Module 540 or the Input Management module 536. Thegestures may be as defined in conjunction with FIGS. 4A through 4H. Forexample, moving a window causes the display to render a series ofdisplay frames that illustrate the window moving. The gesture associatedwith such user interface interaction can be received and interpreted bythe Gesture Module 576. The information about the user gesture is thensent to the Task Management Module 540 to modify the display binding ofthe task.

The Requirements Module 580, similar to the Preferences Module 572, isoperable to determine display requirements for an application 564 orother component. An application can have a set display requirement thatmust be observed. Some applications require a particular displayorientation. For example, the application “Angry Birds” can only bedisplayed in landscape orientation. This type of display requirement canbe determined or received, by the Requirements Module 580. As theorientation of the device changes, the Requirements Module 580 canreassert the display requirements for the application 564. The DisplayConfiguration Module 568 can generate a display configuration that is inaccordance with the application display requirements, as provided by theRequirements Module 580.

The Event Module 584, similar to the Gesture Module 576, is operable todetermine one or more events occurring with an application or othercomponent that can affect the user interface. Thus, the Event Module 584can receive event information either from the event buffer 556 or theTask Management module 540. These events can change how the tasks arebound to the displays. The Event Module 584 can collect state changeinformation from other Framework 520 components and act upon that statechange information. In an example, when the phone is opened or closed orwhen an orientation change has occurred, a new message may be renderedin a secondary screen. The state change based on the event can bereceived and interpreted by the Event Module 584. The information aboutthe events then may be sent to the Display Configuration Module 568 tomodify the configuration of the display.

The Binding Module 588 is operable to bind the applications 564 or theother components to the configuration determined by the DisplayConfiguration Module 568. A binding associates, in memory, the displayconfiguration for each application with the display and mode of theapplication. Thus, the Binding Module 588 can associate an applicationwith a display configuration for the application (e.g. landscape,portrait, multi-screen, etc.). Then, the Binding Module 588 may assign adisplay identifier to the display. The display identifier associated theapplication with a particular display of the device 100. This binding isthen stored and provided to the Display Controller 544, the othercomponents of the OS 516, or other components to properly render thedisplay. The binding is dynamic and can change or be updated based onconfiguration changes associated with events, gestures, state changes,application preferences or requirements, etc.

User Interface Configurations:

With reference now to FIGS. 6A-J, various types of output configurationsmade possible by the device 100 will be described hereinafter.

FIGS. 6A and 6B depict two different output configurations of the device100 being in a first state. Specifically, FIG. 6A depicts the device 100being in a closed portrait state 304 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first portrait configuration 604.As can be appreciated, the first portrait configuration 604 may onlydisplay a desktop or operating system home screen. Alternatively, one ormore windows may be presented in a portrait orientation while the device100 is displaying data in the first portrait configuration 604.

FIG. 6B depicts the device 100 still being in the closed portrait state304, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second portrait configuration 608.

It may be possible to display similar or different data in either thefirst or second portrait configuration 604, 608. It may also be possibleto transition between the first portrait configuration 604 and secondportrait configuration 608 by providing the device 100 a user gesture(e.g., a double tap gesture), a menu selection, or other means. Othersuitable gestures may also be employed to transition betweenconfigurations. Furthermore, it may also be possible to transition thedevice 100 from the first or second portrait configuration 604, 608 toany other configuration described herein depending upon which state thedevice 100 is moved.

An alternative output configuration may be accommodated by the device100 being in a second state. Specifically, FIG. 6C depicts a thirdportrait configuration where data is displayed simultaneously on boththe primary screen 104 and the secondary screen 108. The third portraitconfiguration may be referred to as a Dual-Portrait (PD) outputconfiguration. In the PD output configuration, the touch sensitivedisplay 110 of the primary screen 104 depicts data in the first portraitconfiguration 604 while the touch sensitive display 114 of the secondaryscreen 108 depicts data in the second portrait configuration 608. Thesimultaneous presentation of the first portrait configuration 604 andthe second portrait configuration 608 may occur when the device 100 isin an open portrait state 320. In this configuration, the device 100 maydisplay one application window in one display 110 or 114, twoapplication windows (one in each display 110 and 114), one applicationwindow and one desktop, or one desktop. Other configurations may bepossible. It should be appreciated that it may also be possible totransition the device 100 from the simultaneous display ofconfigurations 604, 608 to any other configuration described hereindepending upon which state the device 100 is moved. Furthermore, whilein this state, an application's display preference may place the deviceinto bilateral mode, in which both displays are active to displaydifferent windows in the same application. For example, a Cameraapplication may display a viewfinder and controls on one side, while theother side displays a mirrored preview that can be seen by the photosubjects. Games involving simultaneous play by two players may also takeadvantage of bilateral mode.

FIGS. 6D and 6E depicts two further output configurations of the device100 being in a third state. Specifically, FIG. 6D depicts the device 100being in a closed landscape state 340 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first landscape configuration 612.Much like the other configurations described herein, the first landscapeconfiguration 612 may display a desktop, a home screen, one or morewindows displaying application data, or the like.

FIG. 6E depicts the device 100 still being in the closed landscape state340, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second landscape configuration 616. It may be possible todisplay similar or different data in either the first or second portraitconfiguration 612, 616. It may also be possible to transition betweenthe first landscape configuration 612 and second landscape configuration616 by providing the device 100 with one or both of a twist and tapgesture or a flip and slide gesture. Other suitable gestures may also beemployed to transition between configurations. Furthermore, it may alsobe possible to transition the device 100 from the first or secondlandscape configuration 612, 616 to any other configuration describedherein depending upon which state the device 100 is moved.

FIG. 6F depicts a third landscape configuration where data is displayedsimultaneously on both the primary screen 104 and the secondary screen108. The third landscape configuration may be referred to as aDual-Landscape (LD) output configuration. In the LD outputconfiguration, the touch sensitive display 110 of the primary screen 104depicts data in the first landscape configuration 612 while the touchsensitive display 114 of the secondary screen 108 depicts data in thesecond landscape configuration 616. The simultaneous presentation of thefirst landscape configuration 612 and the second landscape configuration616 may occur when the device 100 is in an open landscape state 340. Itshould be appreciated that it may also be possible to transition thedevice 100 from the simultaneous display of configurations 612, 616 toany other configuration described herein depending upon which state thedevice 100 is moved.

FIGS. 6G and 6H depict two views of a device 100 being in yet anotherstate. Specifically, the device 100 is depicted as being in an easelstate 312. FIG. 6G shows that a first easel output configuration 618 maybe displayed on the touch sensitive display 110. FIG. 6H shows that asecond easel output configuration 620 may be displayed on the touchsensitive display 114. The device 100 may be configured to depict eitherthe first easel output configuration 618 or the second easel outputconfiguration 620 individually. Alternatively, both the easel outputconfigurations 618, 620 may be presented simultaneously. In someembodiments, the easel output configurations 618, 620 may be similar oridentical to the landscape output configurations 612, 616. The device100 may also be configured to display one or both of the easel outputconfigurations 618, 620 while in a modified easel state 316. It shouldbe appreciated that simultaneous utilization of the easel outputconfigurations 618, 620 may facilitate two-person games (e.g.,Battleship®, chess, checkers, etc.), multi-user conferences where two ormore users share the same device 100, and other applications. As can beappreciated, it may also be possible to transition the device 100 fromthe display of one or both configurations 618, 620 to any otherconfiguration described herein depending upon which state the device 100is moved.

FIG. 6I depicts yet another output configuration that may beaccommodated while the device 100 is in an open portrait state 320.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in aportrait configuration referred to herein as a Portrait-Max (PMax)configuration 624. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Pmaxconfiguration 624 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Pmax configuration 624 to any other outputconfiguration described herein depending upon which state the device 100is moved.

FIG. 6J depicts still another output configuration that may beaccommodated while the device 100 is in an open landscape state 348.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in alandscape configuration referred to herein as a Landscape-Max (LMax)configuration 628. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Lmaxconfiguration 628 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Lmax configuration 628 to any other outputconfiguration described herein depending upon which state the device 100is moved.

The device 100 manages desktops and/or windows with at least one windowstack 700, 728, as shown in FIGS. 7A and 7B. A window stack 700, 728 isa logical arrangement of active and/or inactive windows for amulti-screen device. For example, the window stack 700, 728 may belogically similar to a deck of cards, where one or more windows ordesktops are arranged in order, as shown in FIGS. 7A and 7B. An activewindow is a window that is currently being displayed on at least one ofthe touch sensitive displays 110, 114. For example, windows 104 and 108are active windows and are displayed on touch sensitive displays 110 and114. An inactive window is a window that was opened and displayed but isnow “behind” an active window and not being displayed. In embodiments,an inactive window may be for an application that is suspended, andthus, the window is not displaying active content. For example, windows712, 716, 720, and 724 are inactive windows.

A window stack 700, 728 may have various arrangements or organizationalstructures. In the embodiment shown in FIG. 7A, the device 100 includesa first stack 760 associated with a first touch sensitive display 110and a second stack associated with a second touch sensitive display 114.Thus, each touch sensitive display 110, 114 can have an associatedwindow stack 760, 764. These two window stacks 760, 764 may havedifferent numbers of windows arranged in the respective stacks 760, 764.Further, the two window stacks 760, 764 can also be identifieddifferently and managed separately. Thus, the first window stack 760 canbe arranged in order from a first window 704 to a next window 720 to alast window 724 and finally to a desktop 722, which, in embodiments, isat the “bottom” of the window stack 760. In embodiments, the desktop 722is not always at the “bottom” as application windows can be arranged inthe window stack below the desktop 722, and the desktop 722 can bebrought to the “top” of a stack over other windows during a desktopreveal. Likewise, the second stack 764 can be arranged from a firstwindow 708 to a next window 712 to a last window 716, and finally to adesktop 718, which, in embodiments, is a single desktop area, withdesktop 722, under all the windows in both window stack 760 and windowstack 764. A logical data structure for managing the two window stacks760, 764 may be as described in conjunction with FIG. 8.

Another arrangement for a window stack 728 is shown in FIG. 7B. In thisembodiment, there is a single window stack 728 for both touch sensitivedisplays 110, 114. Thus, the window stack 728 is arranged from a desktop758 to a first window 744 to a last window 756. A window can be arrangedin a position among all windows without an association to a specifictouch sensitive display 110, 114. In this embodiment, a window is in theorder of windows. Further, at least one window is identified as beingactive. For example, a single window may be rendered in two portions 732and 736 that are displayed on the first touch sensitive screen 110 andthe second touch sensitive screen 114. The single window may only occupya single position in the window stack 728 although it is displayed onboth displays 110, 114.

Yet another arrangement of a window stack 760 is shown in FIGS. 7Cthrough 7E. The window stack 760 is shown in three “elevation” views. InFIG. 7C, the top of the window stack 760 is shown. Two sides of thewindow stack 760 are shown in FIGS. 7D and 7E. In this embodiment, thewindow stack 760 resembles a stack of bricks. The windows are stacked oneach other. Looking from the top of the window stack 760 in FIG. 7C,only the top most windows in the window stack 760 are seen in differentportions of the composite display 764. The composite display 764represents a logical model for the entire display area of the device100, which can include touch sensitive display 110 and touch sensitivedisplay 114. A desktop 786 or a window can occupy part or all of thecomposite display 764.

In the embodiment shown, the desktop 786 is the lowest display or“brick” in the window stack 760. Thereupon, window 1 782, window 2 782,window 3 768, and window 4 770 are layered. Window 1 782, window 3 768,window 2 782, and window 4 770 only occupy a portion of the compositedisplay 764. Thus, another part of the stack 760 includes window 8 774and windows 5 through 7 shown in section 790. Only the top window in anyportion of the composite display 764 is actually rendered and displayed.Thus, as shown in the top view in FIG. 7C, window 4 770, window 8 774,and window 3 768 are displayed as being at the top of the display indifferent portions of the window stack 760. A window can be dimensionedto occupy only a portion of the composite display 760 to “reveal”windows lower in the window stack 760. For example, window 3 768 islower in the stack than both window 4 770 and window 8 774 but is stilldisplayed. A logical data structure to manage the window stack can be asdescribed in conjunction with FIG. 8.

When a new window is opened, the newly activated window is generallypositioned at the top of the stack. However, where and how the window ispositioned within the stack can be a function of the orientation of thedevice 100, the context of what programs, functions, software, etc. arebeing executed on the device 100, how the stack is positioned when thenew window is opened, etc. To insert the window in the stack, theposition in the stack for the window is determined and the touchsensitive display 110, 114 to which the window is associated may also bedetermined. With this information, a logical data structure for thewindow can be created and stored. When user interface or other events ortasks change the arrangement of windows, the window stack(s) can bechanged to reflect the change in arrangement. It should be noted thatthese same concepts described above can be used to manage the one ormore desktops for the device 100.

A logical data structure 800 for managing the arrangement of windows ordesktops in a window stack is shown in FIG. 8. The logical datastructure 800 can be any data structure used to store data whether anobject, record, file, etc. The logical data structure 800 can be storedin any type of database or data storage system, regardless of protocolor standard. In embodiments, the logical data structure 800 includes oneor more portions, fields, attributes, etc. that store data in a logicalarrangement that allows for easy storage and retrieval of theinformation. Hereinafter, these one or more portions, fields,attributes, etc. shall be described simply as fields. The fields canstore data for a window identifier 804, dimensions 808, a stack positionidentifier 812, a display identifier 816, and/or an active indicator820. Each window in a window stack can have an associated logical datastructure 800. While only a single logical data structure 800 is shownin FIG. 8, there may be more or fewer logical data structures 800 usedwith a window stack (based on the number of windows or desktops in thestack), as represented by ellipses 824. Further, there may be more orfewer fields than those shown in FIG. 8, as represented by ellipses 828.

A window identifier 804 can include any identifier (ID) that uniquelyidentifies the associated window in relation to other windows in thewindow stack. The window identifier 804 can be a globally uniqueidentifier (GUID), a numeric ID, an alphanumeric ID, or other type ofidentifier. In embodiments, the window identifier 804 can be one, two,or any number of digits based on the number of windows that can beopened. In alternative embodiments, the size of the window identifier804 may change based on the number of windows opened. While the windowis open, the window identifier 804 may be static and remain unchanged.

Dimensions 808 can include dimensions for a window in the compositedisplay 760. For example, the dimensions 808 can include coordinates fortwo or more corners of the window or may include one coordinate anddimensions for the width and height of the window. These dimensions 808can delineate what portion of the composite display 760 the window mayoccupy, which may the entire composite display 760 or only part ofcomposite display 760. For example, window 4 770 may have dimensions 880that indicate that the window 770 will occupy only part of the displayarea for composite display 760, as shown in FIGS. 7c through 7E. Aswindows are moved or inserted in the window stack, the dimensions 808may change.

A stack position identifier 812 can be any identifier that can identifythe position in the stack for the window or may be inferred from thewindow's control record within a data structure, such as a list or astack. The stack position identifier 812 can be a GUID, a numeric ID, analphanumeric ID, or other type of identifier. Each window or desktop caninclude a stack position identifier 812. For example, as shown in FIG.7A, window 1 704 in stack 1 760 can have a stack position identifier 812of 1 identifying that window 704 is the first window in the stack 760and the active window. Similarly, window 6 724 can have a stack positionidentifier 812 of 3 representing that window 724 is the third window inthe stack 760. Window 2 708 can also have a stack position identifier812 of 1 representing that window 708 is the first window in the secondstack 764. As shown in FIG. 7B, window 1 744 can have a stack positionidentifier 812 of 1, window 3, rendered in portions 732 and 736, canhave a stack position identifier 812 of 3, and window 6 756 can have astack position identifier 812 of 6. Thus, depending on the type ofstack, the stack position identifier 812 can represent a window'slocation in the stack.

A display identifier 816 can identify that the window or desktop isassociated with a particular display, such as the first display 110 orthe second display 114, or the composite display 760 composed of bothdisplays. While this display identifier 816 may not be needed for amulti-stack system, as shown in FIG. 7A, the display identifier 816 canindicate whether a window in the serial stack of FIG. 7B is displayed ona particular display. Thus, window 3 may have two portions 732 and 736in FIG. 7B. The first portion 732 may have a display identifier 816 forthe first display while the second portion 736 may have a displayidentifier 816 for the second display 114. However, in alternativeembodiments, the window may have two display identifier 816 thatrepresent that the window is displayed on both of the displays 110, 114,or a display identifier 816 identifying the composite display. Inanother alternate embodiment, the window may have a single displayidentifier 816 to represent that the window is displayed on both of thedisplays 110, 114.

Similar to the display identifier 816, an active indicator 820 may notbe needed with the dual stack system of FIG. 7A, as the window in stackposition 1 is active and displayed. In the system of FIG. 7B, the activeindicator 820 can indicate which window(s) in the stack is beingdisplayed. Thus, window 3 may have two portions 732 and 736 in FIG. 7.The first portion 732 may have an active indicator 820 while the secondportion 736 may also have an active indicator 820. However, inalternative embodiments, window 3 may have a single active indicator820. The active indicator 820 can be a simple flag or bit thatrepresents that the window is active or displayed.

An embodiment of a method 900 for creating a window stack is shown inFIG. 9. While a general order for the steps of the method 900 is shownin FIG. 9. Generally, the method 900 starts with a start operation 904and ends with an end operation 928. The method 900 can include more orfewer steps or can arrange the order of the steps differently than thoseshown in FIG. 9. The method 900 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method900 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-8.

A multi-screen device 100 can receive activation of a window, in step908. In embodiments, the multi-screen device 100 can receive activationof a window by receiving an input from the touch sensitive display 110or 114, the configurable area 112 or 116, a gesture capture region 120or 124, or some other hardware sensor operable to receive user interfaceinputs. The processor may execute the Task Management Module 540 mayreceive the input. The Task Management Module 540 can interpret theinput as requesting an application task to be executed that will open awindow in the window stack.

In embodiments, the Task Management Module 540 places the user interfaceinteraction in the task stack 552 to be acted upon by the DisplayConfiguration Module 568 of the Multi-Display Management Module 524.Further, the Task Management Module 540 waits for information from theMulti-Display Management Module 524 to send instructions to the WindowManagement Module 532 to create the window in the window stack.

The Multi-Display Management Module 524, upon receiving instruction fromthe Task Management Module 540, determines to which touch portion of thecomposite display 760, the newly activated window should be associated,in step 912. For example, window 4 770 is associated with the a portionof the composite display 764 In embodiments, the device state module 574of the Multi-Display Management Module 524 may determine how the deviceis oriented or in what state the device is in, e.g., open, closed,portrait, etc. Further, the preferences module 572 and/or requirementsmodule 580 may determine how the window is to be displayed. The gesturemodule 576 may determine the user's intentions about how the window isto be opened based on the type of gesture and the location of where thegesture is made.

The Display Configuration Module 568 may use the input from thesemodules and evaluate the current window stack 760 to determine the bestplace and the best dimensions, based on a visibility algorithm, to openthe window. Thus, the Display Configuration Module 568 determines thebest place to put the window at the top of the window stack 760, in step916. The visibility algorithm, in embodiments, determines for allportions of the composite display, which windows are at the top of thestack. For example, the visibility algorithm determines that window 3768, window 4 770, and window 8 774 are at the top of the stack 760 asviewed in FIGS. 7C through 7E. Upon determining where to open thewindow, the Display Configuration Module 568 can assign a displayidentifier 816 and possibly dimensions 808 to the window. The displayidentifier 816 and dimensions 808 can then be sent back to the TaskManagement Module 540. The Task Management Module 540 may then assignthe window a stack position identifier 812 indicating the windowsposition at the top of the window stack.

In embodiments, the Task Management Module 540 sends the window stackinformation and instructions to render the window to the WindowManagement Module 532. The Window Management Module 532 and the TaskManagement Module 540 can create the logical data structure 800, in step924. Both the Task Management Module 540 and the Window ManagementModule 532 may create and manage copies of the window stack. Thesecopies of the window stack can be synchronized or kept similar throughcommunications between the Window Management Module 532 and the TaskManagement Module 540. Thus, the Window Management Module 532 and theTask Management Module 540, based on the information determined by theMulti-Display Management Module 524, can assign dimensions 808, a stackposition identifier 812 (e.g., window 1 782, window 4 770, etc.), adisplay identifier 816 (e.g., touch sensitive display 1 110, touchsensitive display 2 114, composite display identifier, etc), and anactive indicator 820, which is generally always set when the window isat the “top” of the stack. The logical data structure 800 may then bestored by both the Window Management Module 532 and the Task ManagementModule 540. Further, the Window Management Module 532 and the TaskManagement Module 540 may thereinafter manage the window stack and thelogical data structure(s) 800.

Demand for portable electronic devices with high levels of functionalitycontinues to rise and personal electronic devices continue to becomeincreasingly more portable. While computer power, battery life, screensize and overall functionality of portable phones and smart phonescontinues to increase, user reliance on these devices increases. Manyusers of such devices rely heavily on such devices for generalcommunication, accessing the internet, cloud computing, and accessingvarious locally stored information such as contact information, files,music, pictures and the like. It is often desirable therefore to connectsuch heavily relied on devices to an additional computing device ordisplay, such as a monitor or tablet device, such as a SmartPad (SP)1000 (see FIG. 10).

Accordingly, it is desirable for the device 100 to be able to interfacewith an additional device, such as the SmartPad 1000, that enablesfunctionality similar to, for example, both a tablet computer system andsmart phone. Furthermore, a need exists for the above-described deviceto allow for various pre-existing features of both devices, such assending and receiving phone calls and further allowing for theaccessibility of applications running on the device 100. A need alsoexists for the above device 100 to provide the benefits of both a tabletcomputer system and cellular phone in one integrative device by allowingfor common operations and functionality without compromising the formfactor of the device.

One exemplary embodiment is directed toward a selectively removabledevice and smartpad system. The smartpad system is discussed in greaterdetail hereinafter, and can have various features for complementing thecommunications device, such as a smart phone or device 100. For example,the smartpad may supplement the device 100 by providing increased screensize, increased processor size, increased battery or power supply, orthe like. Similarly, the device 100 may compliment the SP 1000 byproviding connectivity through one or more wireless networks, access tovarious stored information, and the like. It will expressly recognizetherefore that two or more devices of the present invention may beprovided in a connected or docked and generally symbiotic relationship.It will further be recognized that the devices provide various features,benefits and functionality in their independent state(s).

In accordance with one exemplary embodiment, the device 100 is capableof being received by the SP 1000 through a recessed feature of the SP1000 having corresponding dimensions to the device 100. In one exemplaryembodiment, the SP 1000 is provided and preferably sized for receiving apredetermined device 100. In alternative embodiments, however, it iscontemplated that the SP 1000 is provided, the smartpad capable ofreceiving a plurality of communications devices of different sizes. Insuch embodiments, the SP 1000 may receive communications devices ofvarious sizes by, for example, the inclusion of additional elements,such as spacers and various adjustable features.

In accordance with one exemplary embodiment, the device 100 and SP 1000have a docking relationship that is established when the device 100 isconnected to the SP 1000 during various modes of operation. For example,in one embodiment, a system is provided comprising the SP 1000 and thedevice 100, the SP 1000 capable of physically receiving the device 100,wherein the device 100 is operable as the primary computing device. Insuch an embodiment, the SP 1000 may, for example, simply provideenhanced audio and visual features for the device 100 that comprises itsown CPU, memory, and the like. It is further contemplated that thesystem can be placed in a mode of operation wherein the device 100docked to the SP 1000 provide it in a more passive mode where, forexample, the device 100 draws power from the SP 1000 such as to rechargea battery of the device 100.

In accordance with another exemplary embodiment, the device 100 and SP1000 are provided wherein the device 100 is received or docked with theSP 1000 and wherein a substantial area of the device 100 is positionedwithin one or more compartments of the SP 1000. For example, where asvarious known devices comprise docking features which require or resultin the docked item to be generally exposed, thereby substantiallyaltering the external dimensions of the host device and/or creating apotential for damaging one or both devices upon impact, an exemplaryembodiment contemplates the SP 1000 which receives the device 100 in amanner such that the external dimensions of the SP 1000 are notsubstantially altered when the devices are connected. In such anarrangement, the device 100 and associated connection means aregenerally protected and the SP 1000 is allowed to substantially maintainits original shape. In accordance with one exemplary embodiment, the SP1000 is capable of receiving and/or docking the device 100 wherein thedevice 100 is received in lockable association with the SP 1000. As usedherein, the term “lockable” is not intended to designate or limit it toany particular arrangement. Rather, lockable is intended to refer tovarious embodiments as described herein and will be recognized by one ofordinary skill in the art. In one embodiment, the device 100 isconnectable to the SP 1000 wherein the SP 1000 comprises extensionsprings for first electively securing the device 100 in a docked mannerand an ejection feature for releasing the device 100 from the SP 1000.Moreover, as will be described in greater detail below, it should beappreciated that the device 100 and SP 1000 can communicate using wiredand/or wireless technology(ies) with equal success. Moreover, and inaccordance with another exemplary embodiment, the hinged device 100 isselectively connectable to the SP 1000 wherein the device 100 isreceived by the SP 1000 in an open position and where in one or morepreexisting ports of the SP 1000 correspond with internal receivingfeatures of the SP 1000, such that the device 100 and the SP 1000 may beoperated simultaneously in various modes of use.

In accordance with some exemplary embodiments, the SP 1000 is providedwith an eject or release button to facilitate the removal of a stored ordocked device 100.

FIG. 10 illustrates an exemplary SmartPad (SP) 1000 according to anexemplary embodiment. The exemplary SmartPad at least provides a largertouch sensitive display operatively coupleable to device 100.

While the following description uses the term “smart” in conjunctionwith the display device 1000, it is to be appreciated that this termdoes not necessarily connotate that there is intelligence in theSmartPad. Rather, it is to be appreciated that there can be“intelligence,” including one or more of a processor(s), memory,storage, display drivers, etc., in the SmartPad, and/or one or more ofthese elements shared with the device 100 via, for example, one or moreof a port, bus, connection, or the like. In general, any one or more ofthe functions of the device 100 is extendable to the SmartPad 1000 andvice versa.

The exemplary SmartPad 1000 includes a screen 1004, a SP touch sensitivedisplay 1010, a SP configurable area 1008, a SP gesture captureregion(s) 1020 and a SP camera 1016. The SP 1000 also includes a port(not visible in this orientation) adapted to receive the device 100 asillustrated at least in FIG. 11.

The device 100 docks with the SmartPad 1000 via the port on the SP 1000and the corresponding port 136 on device 100. As discussed, port 136 insome embodiments is an input/output port (I/O port) that allows thedevice 100 to be connected to other peripheral devices, such as adisplay, keyboard, printing device and/or SP 1000. In accordance withone exemplary embodiment, the docking is accomplished by the device 100sliding into the left-hand side of the SP 1000, with the device 100being in an open state and the device 100 engaging a port in the SP 1000corresponding to port 136. In accordance with one exemplary embodiment,the device 100 engages a doored cassette-like slot in the SP 1000 intowhich the device 100 slides. (See for example FIGS. 13A-B.) It should beappreciated however that there may be other configurations forphysically and electrically engaging the two devices—in general, themanner of engagement is not important provided the device 100 and SP1000 are in electrical communication with one another.

The SP 1000 includes a screen 1004. In some embodiments, the entirefront surface of the SP 1000 may be touch sensitive and capable ofreceiving input by a user touching the front surface of the screen 1004.The screen 1004 includes touch sensitive display 1010, which, inaddition to being touch sensitive, is also capable of displayinginformation to a user.

The screen 1004 also includes a configurable area 1008 that has beenconfigured for specific inputs when the user touches portions of theconfigurable area 1008. Area 1012 a is configured to receive a “back”input indicating that a user would like to view information previouslydisplayed. Area 1012 b is configured to receive a “menu” inputindicating that the user would like to view options from a menu. Area1012 c is configured to receive a “home” input indicating that the userwould like to view information associated with a “home” view.

In other embodiments, areas 1012 a-c may be configured, in addition tothe configurations described above, for other types of specific inputsincluding controlling features of device 100 and/or device 1000, somenon-limiting examples including adjusting overall system power,adjusting the volume, adjusting the brightness, adjusting the vibration,selecting of displayed items on screen 1004, operating the SP camera1016, operating a microphone, and initiating/terminating of telephonecalls. Also, in some embodiments, areas 1012 a-c may be configured forspecific inputs depending upon the application running on device 100/SP1000 and/or information displayed on the touch sensitive displays 1010.

In addition to touch sensing, screen 1004 may also include areas thatreceive input from a user without requiring the user to touch thedisplay area of the screen. For example, screen 1004 can include gesturecapture area 1020. These areas are able to receive input by recognizinggestures made by a user without the need for the user to actually touchthe surface of the display area. In comparison to touch sensitivedisplay 1010 and 1014, the gesture capture area 1020 may not be capableof rendering a displayed image.

While not illustrated, there may also be a number of hardware componentswithin SP 1000. As illustrated in FIG. 10, SP 1000 can include aspeaker, a microphone and one or more cameras 1016. Upon docking thedevice 100 in the SP 1000, the corresponding device(s) (e.g., thespeaker) in the device 100 could be disabled in favor of the speaker inthe SP 1000. Similarly, other components, such as the screen 1004,microphone, speaker, etc, could be disabled on the device 100 in favorof the SP 1000.

In general, the touch sensitive display 1010 may comprise a full color,touch sensitive display. A second area within each touch sensitivescreen 1004 may comprise the SP gesture capture region 1020. The SPgesture capture region 1020 may comprise an area or region that isoutside of the SP touch sensitive display 1010 area that is capable ofreceiving input, for example in the form of gestures provided by a user.However, the SP gesture capture region 1020 does not necessarily includepixels that can perform a display function or capability.

A third region of the SP touch sensitive screen 1004 may comprise theconfigurable area 1008. The configurable area 1008 is capable ofreceiving input and has display or limited display capabilities. Inembodiments, the configurable area 1008 may present different inputoptions to the user. For example, the configurable area 1008 may displaybuttons or other relatable items. Moreover, the identity of displayedbuttons, or whether any buttons are displayed at all within theconfigurable area 1008 of the SP touch sensitive screen 1004 may bedetermined from the context in which the device 1000 is used and/oroperated. In an exemplary embodiment, the touch sensitive screen 1004comprise liquid crystal display devices extending across at least thoseregions of the touch sensitive screen 1004 that is capable of providingvisual output to a user, and a capacitive input matrix over thoseregions of the touch sensitive screen 1004 that is capable of receivinginput from the user.

As discussed above with reference to FIGS. 4A through 4H, the variousgraphical representations of gesture inputs that may be recognized bythe screens 104, 108 are also recognizable by screen 1004. As discussed,the gestures may be performed not only by a user's body part, such as adigit, but also by other devices, such as a stylus, that may be sensedby the contact sensing portion(s) of a screen 1004. In general, gesturesare interpreted differently, based on where the gestures are performed(either directly on the display 1004 or in the gesture capture region1020). For example, gestures in the display 1010 may be directed to adesktop or application, and gestures in the gesture capture region 1020may be interpreted as for the system.

In addition to the above, the SP touch sensitive screen 1004 may alsohave an area that assists a user with identifying which portion of thescreen is in focus. This could be a bar of light or in general anindicator that identifies which one or more portions of the SP touchsensitive screen 1004 are in focus. (See for example, FIG. 29)

One or more display controllers (such as display controllers 216 a, 216b and/or dedicated display controller(s) on the SP 1000) may be providedfor controlling the operation of the touch sensitive screen 1004including input (touch sensing) and output (display) functions.

In accordance with one exemplary embodiment, a separate touch screencontroller is provided for the SP 1000 in addition to each of thecontrollers for the touch screens 104 and 108. In accordance withalternate embodiments, a common or shared touch screen controller may beused to control any one or more of the touch sensitive screens 104 and108, and/or 1004. In accordance with still other embodiments, thefunctions of the touch screen controllers may be incorporated into othercomponents, such as a processor and memory or dedicated graphicschip(s).

In a similar manner, the SP 1000 may include a processor complementaryto the processor 204, either of which may comprise a general purposeprogrammable processor or controller for executing applicationprogramming or instructions. In accordance with at least someembodiments, the processors may include multiple processor cores, and/orimplement multiple virtual processors. In accordance with still otherembodiments, the processors may include multiple physical processors. Asa particular example, the processors may comprise a specially configuredapplication specific integrated circuit (ASIC) or other integratedcircuit, a digital signal processor, a controller, a hardwiredelectronic or logic circuit, a programmable logic device or gate array,a special purpose computer, or the like. The processors generallyfunction to run programming code or instructions implementing variousfunctions of the device 100 and/or SP 1000.

The SP 1000 can also optionally be equipped with an audio input/outputinterface/device(s) (not shown) to provide analog audio to aninterconnected speaker or other device, and to receive analog audioinput from a connected microphone or other device. As an example, theaudio input/output interface/device(s) 256 may comprise an associatedamplifier and analog to digital converter usable with SP 1000.Alternatively or in addition, the device 100 can include an integratedaudio input/output device 256 and/or an audio jack for interconnectingan external speaker or microphone via SP 1000. For example, anintegrated speaker and an integrated microphone can be provided, tosupport near talk or speaker phone operations.

Hardware buttons (not shown) but similar to hardware buttons 158 can beincluded for example for use in connection with certain controloperations. Examples include a master power switch, volume control,etc., as described in conjunction with FIGS. 1A through 1J. One or moreimage capture interfaces/devices 1016, such as a camera, can be includedfor capturing still and/or video images. Alternatively or in addition,an image capture interface/device 1016 can include a scanner or codereader. An image capture interface/device 1016 can include or beassociated with additional elements, such as a flash or other lightsources.

Communications between various components of the device 100 and SP 1000can be carried by one or more buses and/or communications channels. Inaddition, power can be supplied to one or more of the components of thedevice 100 and Sp 1000 from a power source and/or power control module260. The power control module 260 and/or device 100 and/or SP 1000 can,for example, include a battery, an AC to DC converter, power controllogic, and/or ports for interconnecting the device 100/1000 to anexternal source of power.

The middleware 520 may also be any software or data that allows themultiple processes running on the devices to interact. In embodiments,at least portions of the middleware 520 and the discrete componentsdescribed herein may be considered part of the OS 516 or an application564. However, these portions will be described as part of the middleware520, but those components are not so limited. The middleware 520 caninclude, but is not limited to, a Multi-Display Management (MDM) class524, a Surface Cache class 528, a Window Management class 532, anActivity Management class 536, an Application Management class 540, adisplay control block, one or more frame buffers 548, an activity stack552, and/or an event buffer 556—all of the functionality thereofextendable to the SP 1000. A class can be any group of two or moremodules that have related functionality or are associated in a softwarehierarchy.

The MDM class 524 also includes one or more modules that are operable tomanage the display of applications or other data on the screen of the SP1000. An embodiment of the MDM class 524 is described in conjunctionwith FIG. 5B. In embodiments, the MDM class 524 receives inputs from theOS 516, the drivers 512 and the applications 564. The inputs assist theMDM class 524 in determining how to display the information required bythe user. Once a determination for display configurations is determined,the MDM class 524 can bind the applications 564 to a displayconfiguration. The configuration may then be provided to one or moreother components to generate the display on the SP 1000.

FIG. 11 illustrates an exemplary embodiment showing the device 100docking with the SP 1000. More specifically, the device 100 is beinginserted into a slot (not shown) on the SP 1000. On completion of theinserting of device 100 into SP 1000 (See FIG. 12), device 100communicates with the SP 1000 via bus or other wired or wirelesselectrical means 1204. The device 100 is also connected with, forexample, the camera/video camera 1016, microphone (Mic), and power port1208.

In conjunction with the docking of device 100 with SP 1000, one or moreof the devices can begin power management. For example, one or more ofthe device 100 and SP 1000 can include power supplies, such asbatteries, solar, or in general any electrical supply, any one or moreof which being usable to supply one or more of the device 100 and SP1000. Furthermore, through the use of, for example, an AC power adaptorconnected to port 1208, the SP 1000 can supply power to device 100, suchas to charge device 100. It will be appreciated that the powermanagement functionality described herein can be distributed between oneor more of the device 100 and SP 1000, with power being sharable betweenthe two devices.

In addition to power management functions, upon the device 100 beingdocked with the SP 1000, the displays on device 100 can be turned offto, for example, save power. Furthermore, electrical connections areestablished between the device 100 and SP 1000 such that the speaker,microphone, display, input capture region(s), inputs, and the like,received by SP 1000 are transferable to device 100. Moreover, thedisplay on device 1000 is enabled such that information that would havebeen displayed on one or more of the touch sensitive displays 110 and114 is displayed on touch sensitive display 1010. As will be discussedin greater detail herein, the SP 1000 can emulate the dual displayconfiguration of the device 100 on the single display 1010.

The SP 1000 can optionally be equipped with the headphone jack 1212 andpower button 1216. Moreover, any hardware buttons or user input buttonson the device 100 could be extended to and replicated on the SP 1000.

This dock event between the device 100 and SP 1000 can be seen as states336 or 344 in FIG. 3A. As will be appreciated, and in accordance withone of the illustrative embodiments herein, the device 100 is dockedwith SP 1000 with the device being in the open state 210. However, it isto be appreciated that the device 100 can be docked with the SP 1000 inthe closed state 304, or docked via, for example, a cable without thedevice 100 necessarily being inserted into the SP 1000.

FIGS. 13A-B illustrate application reorientation according to anexemplary embodiment of the invention. In particular, FIG. 13Aillustrates the device 100 being inserted into the SP 1000. Before beingassociated with the SP 1000, the device 100 has two applications, bothin the landscape mode, represented by application “B” in landscape on afirst screen and application “C” in landscape on a second screen(partially obscured by SP 1000).

FIG. 13B illustrates the re-orientation of the windows for the twoapplications based on the device 100 being associated with the SP 1000,the SP 1000 being in the landscape orientation. In accordance with thisexemplary embodiment, application “B” on the device 100 is re-orientedto be in the portrait orientation on the SP 1000, and in a similarmanner, application “C” on the device 100 is reoriented to the portraitorientation on the right-hand side the touch sensitive display 1010. Aswill be appreciated, the reorientation of the application(s) from thedevice 100 to the SP 1000 can occur in a similar manner for a singleapplication running on the device 100. For example, if there is only oneapplication running on device 100, and the application is running inlandscape mode, when the device 100 is docked with the SP 1000, theorientation of the application is reoriented to be appropriate for thecurrent orientation of the SP 1000. For example, if the application onthe device 100 is in portrait mode, and the SP 1000 is in landscapemode, the application is reoriented from portrait mode on the device 100to landscape mode on the SP 1000. In a similar manner, if theapplication on the device is in landscape mode, and upon being docked tothe SP 1000 in portrait mode, the application is reoriented intoportrait mode for appropriate viewing on the SP 1000.

In accordance with one exemplary embodiment, the accelerometer 176 ondevice 100 is used to determine the orientation of both the device 100and SP 1000, and consequently the orientation of the touch screendisplay 1010. Therefore, the accelerometer(s) 176 outputs a signal thatis used in connection with the display of information to control theorientation and/or format in which information is to be displayed to theuser on display 1010. As is to be appreciated, reorientation can includeone or more of a portrait to landscape conversion, a landscape toportrait conversion, a resizing, a re-proportioning and/or a redrawingof the window(s) associated with the application(s).

On reorienting of the running application(s), the application(s) isdisplayed on display 1010 on SP 1000.

In accordance with an optional exemplary embodiment, priority can begiven to the application that is in focus. For example, and using againapplications “B” and “C” as illustrated in FIG. 13B, if insteadapplication C was in focus before docking, application C could bereoriented and displayed on the left-hand portion of display 1010, andapplication B, which was not in focus before docking, displayed on theright-hand portion of display 1010 upon docking.

In accordance with another optional embodiment, the application in focuscould be displayed in full-screen mode on display 1010 with theapplication(s) not in focus placed into a window stack that is, forexample, in a carousel-type arrangement as discussed hereinafter.

FIG. 14 illustrates an exemplary embodiment of a single application modefor the SP 1000. In the single application mode, all applications arelaunched and displayed in full screen. The single application mode canbe indicated by a multi-tasking icon in the annunciator bar, or at someother location on screen 1004.

Displaying of the application(s) are managed by one or more of thedisplay controller 544, framework 520, window management module 532,display configuration module 568, as well as middleware 520 andassociated classes. In single application mode, all dual screen capableapplications can be launched in either a dual screen or max mode, wherethe application is displayed substantially filling the display 1010.This is applicable to when the SP 1000 is either in the portrait mode,as illustrated in FIG. 14, or in the landscape mode, as illustrated inFIG. 15. In these figures, the “A” represents the single applicationwith the X1, X2 being variables representing the coordinates and/orlocation of the window in which the application “A” is to be displaced.A similar notation is used hereinafter for the multi-application mode,with it being appreciated that, for example, X1 may contain thecoordinate information for the displaying of the window for a firstapplication, and X2 may contain the coordinate information for thedisplaying of a window corresponding to a second application, and so on.

Therefore, in one exemplar embodiment, when a single application isexecuted, a single application can launch in the full screen mode andcan be correlated to the max mode as discussed in relation to FIG. 6Iwhere a single application spans both screens of the device 100. Thismax mode is applicable to both the portrait and landscape orientationsas illustrated in FIG. 14 and FIG. 15 with the display configurationmodule 568 appropriately (re)sizing the window for the application tofit on substantially all or all of the display 1010.

This resizing can occur regardless of whether a native application onthe device 100 actually supports the orientation of the SP 1000.Therefore, even if the application does not support a particularorientation on device 100, the display configuration module 568 canappropriately re-render and/or re-size the window for the applicationfor appropriate display on the SP 1000.

FIG. 16 and FIG. 17 illustrate an exemplary method of rendering a singleapplication, which is a dual screen application, in the portrait maxmode and landscape max mode, respectively. More specifically, in FIG.16, the rendering of a dual screen application in portrait mode willdisplay on display 1010 one of the two screens substantially orcompletely filling display 1010. A user then, for example using agesture, could scroll between the two screens of the single application.In the landscape mode, as illustrated in FIG. 17, the screen 1010 isdivided into a first portion 1704 and a second portion 1708. In thisexemplary embodiment, the first screen of the dual screen application isrendered in first portion 1704, and the second screen of the dual screenapplication is rendered in the second portion 1708. While a certainportion of the screen 1010 is illustratively logically divided for thefirst portion 1704 and the second portion 1708, it should be appreciatedthat the screen real estate assigned to each portion can vary, forexample, based on one or more of optimum display for the window(s), typeof information being displayed in each portion, user preferences, rulesassociated with the application, and/or the like.

In accordance with a first example, the first portion is allocated onethird of the screen 1010's resolution, while the second portion 1708 isallocated two thirds of the screen real estate. In accordance withanother example, the screen 1010 is split 50/50. In accordance with yetanother example, the first portion could be allocated 70% of the screen1010's real estate, while the second portion 1708 could be allocated30%. The managing and resizing of these windows can again be done incooperation with the display configuration module 568, as well as thewindows management module 532 and display controllers for successfulrendering of the location of the window(s) on the SP 1000.

As will be appreciated, and in a manner similar to the operation ofdevice 1000, should the SP 1000 change orientation (e.g., from landscapeto portrait or vice versa) the window(s) for the application(s) can beredrawn in the appropriate orientation taking into account windowprioritization based on whether a particular application and currentfocus is for a dual screen application or a single screen application.

Focus can also be taken into consideration when determining which windowof the application should be displayed when the SP 1000 is in theportrait position. For example, if the application is an e-mail client,and the application natively is displayed on dual screens on device 1000(a first screen being directed toward showing inbox content, and thesecond screen being a preview window for a specific item in the inbox)the system can evaluate which window is currently in focus, and ensurethat window is displayed in the portrait max mode when the SP 1000 is inthe portrait orientation.

In FIG. 17 the SP 1000 is configured to merge windows from the dualscreen application on to a single display 1010. In this landscapeorientation, data (e.g., a single image, application, window, icon,video, etc.) from a first window is displayed in a first portion of thedisplay 1010 while data (e.g., a single image, application, window,icon, video, etc.) is shown in a second portion of the display 1010.Similar to other output configurations, it may be possible to transitionthe SP 1000 from the shown output configuration to any other outputconfiguration described herein, depending on, for example, into whichstate the SP 1000 is moved.

Some other exemplary embodiments of windows management within the SP1000 upon the device 100 docking with the SP 1000 are as follows: Forexample, a device 100 is docked to the SP 1000, with the SP 1000 in aportrait orientation and there are two single-screen applicationsrunning on the device 1000, the application in focus is placed in alower portion of the display 1010, and the application not in focus isplaced on an upper portion of the display 1010. Another exemplaryscenario, where the device 100 is docked to a portrait-oriented SP 1000where one dual-screen application is running on the device 100 and theSP 1000 is in a dual application mode, applies gravity drop as discussedherein.

In another exemplary scenario, where the device 100 is running twosingle-screen applications, and the SP 1000 is in a landscape dualapplication mode, the first application is assigned to a first portionof the display 1010 and the second application is assigned to a secondportion of the display 1010.

In yet another exemplary scenario where the device 100 is running onedual-screen application and the SP 1000 is in dual application landscapemode, both screens of the dual screen application can be shown on the SP1000.

Stickiness can also apply to the SP 1000 such that, for example, when afirst application is in focus, upon docking to a single application modeSP 1000, the application remains visible after docking. As anotherexample of stickiness, if a second application is in focus upon dockingto a single application mode SP 1000, application two remains visibleafter docking.

In accordance with another example, the device 100 is running onedual-screen application and is docked to a landscape-oriented SP 1000 inmax mode, the windows are re-oriented to be side-by-side, opposed to oneabove the other.

FIGS. 18 through FIG. 21 generally illustrate the management and displayof a virtual keyboard 1804 on display 1010. More specifically, in FIG.18, in portrait mode, the virtual keyboard 1804 is positioned belowapplication area 1808, where an application is displayed in, forexample, max mode. In general, it is preferred that the keyboard can beglued to the lower-portion of the display 1010, regardless of whetherthe SP is in the landscape or portrait mode. However, it is to beappreciated that, for example, based on user preferences, the screen canbe glued to another portion of the screen, or can be moved to anotherlocation via, for example, a gesture. In FIG. 18, the application area1808 displays, for example, a standard application with the virtualkeyboard 1804 being displayed in the lower portion of display 1010. InFIG. 19, for example, the application area 1908 is showing a dual-screenenabled application in max mode. The keyboard 1804 is again similarlydisplayed in the lower portion of the display 1010.

In FIG. 20, in SP landscape mode, the keyboard 1804 is displayed in thelower portion of display 1010 with the application area 2004substantially or completely filling the displayable area above thekeyboard 1804. In FIG. 21, the SP is again in landscape mode anddisplaying a dual-screen enabled application in max mode, theapplication area 1 2104 and application area 2 2108, the keyboard 1804is displayed below the two application areas.

In general, in the embodiments illustrated in FIG. 18 through FIG. 21, afirst determination is made as to whether a keyboard should bedisplayed. If the keyboard is to be displayed, the next determination ismade as to the orientation of the SP. If the SP is in a portrait mode,the virtual keyboard is presented also in a portrait mode, preferable onthe lower portion of the screen. If the SP is in a landscape mode, thekeyboard is optionally re-sized to be substantially displayed on a lowerportion of the display with, for example, one or more applicationwindows being located above the virtual keyboard. With the orientationof the SP change, the keyboard is also reoriented to be coincident withthe orientation of the SP. Similarly, when the keyboard is no longerrequired, the keyboard is hidden with the application area(s) beingexpanded to again substantially fill the display 1010.

FIG. 22 and FIG. 23 illustrate exemplary methods of managing windowpositions on the SP 1000. In particular, in FIG. 22, application X 2204is in view on display 1010. On receiving user input, such as the swipemotion represented by 2208 in the gesture capture region 1020,application X is “scrolled” to the left to be replaced with thedual-screen application A1|A2, as shown in FIG. 23. If the same gesture2208 were to be repeated again, application Z would come into view.Similarly, if in FIG. 22 gesture 2208 was in the opposite direction, tothe right, application Y would come into view on display 1010. Scrollingthrough available windows is of course applicable to both the landscapeand portrait mode of the SP in a similar manner. For example, inportrait mode, instead of the gesture traversing from left to right orright to left, the gesture could traverse in a downward motion, or in anupward motion, with the virtual stacks of the windows being located“above” or “below” the device, similar to a rolodex. Thus, when the userinitiates a downward type gesture, the next application “above” isdisplayed on display 1010.

FIG. 24 illustrates the multi application mode of the SP 1000, whereinin the multi application mode the SP 1000 emulates the device 100 in itsmini-tablet form—with this mode optionally being invoked by selection ofa multi application button (shown and described hereinafter). Asimplified way of understanding this mode is to appreciate that the modeemulates the device 100 being opened. In this multi application mode,the SP 1000 can inherit the rules regarding the display of informationon the device 100—For example, that all applications are launched insingle screen mode. One exception could be applications that support amax mode can be by default automatically expanded to this mode ifprovided the opportunity.

In this mode, each application has the ability to determine how theapplication appears in each orientation (e.g., portrait and landscape).

FIG. 26 illustrates an exemplary method of managing the multipleapplication mode of the SP 1000. In the multiple application mode,multiple applications can be managed and displayed within the display1010. In multi application mode, the SP1000 having the single screenemulates the dual screens of the device 100. To initiate the multipleapplication mode, a button/toggle 2618 is selected, which allows theuser to select multiple applications for display in the display 1010. Inthis exemplary embodiment, a first application 2604 C, is shown in theupper-portion of the portrait mode SP 1000 and a second application 2608D, is shown in a lower-portion of screen 1010. In conjunction with thedisplaying of multiple applications in the multiple application mode,focus indicator 2616 can be provided to assist the user with identifyingwhich application is in focus. As discussed, this focus indicator 2616can be a light bar, or other indicator (such as an indicator in thescreen 1010 or beside 2608) drawing the user's attention to whichapplication is in focus. In the exemplary embodiment in FIG. 26,application D 2608 is in focus as represented by the focus indicator2616. In accordance with this exemplary embodiment, and while the focusindicator 2616 is shown in the gesture capture region 1020, it should beappreciated that the focus indicator could be located in some otherportion of the SP 1000. For example, the window for the application infocus could be slightly re-sized to allow for the display of a bar ofpixels adjacent to the window, which would similarly alert the user tothe fact that that application is in focus. Similarly, the applicationin focus could appear at normal brightness while the application not infocus could be slightly dimmed. In general, any technique could be usedto assist the user in readily determining which application is in focus.

To change focus, a user could use any of the gestures discussed hereinor could, for example, simply touch the area where application C isdisplayed, thereby changing focus to application C, at which point acorresponding relocation of the focus indicator 2616 to adjacent toapplication C would occur.

FIG. 27 illustrates a similar scenario for a landscape mode SP 1000. Inparticular, and upon selection of the multi application mode, thedisplay 1010 is divided between, in this example, a first application D2712, and a second application F 2708. Here, application D is displayedon the right-hand portion of display 1010 and application F displayed onthe left-hand portion of display 1010. While in this exemplaryembodiment, the display real estate is split 50/50 between the twoapplications, it should be appreciated that one application could bedisplayed on a larger portion of the display 1010 than the other. Inthis particular exemplary embodiment, application D is in focus, asrepresented by focus indicator 2416.

In the multiple application mode, in both portrait and landscapeorientations, each application could have its own associated windowstack as show in FIG. 22 and FIG. 23, or there could be one stack sharedbetween all of the displayed applications. More specifically, if eachapplication has its own stack, with a stack structure similar to thatillustrated in FIG. 22, a stack would be available for the firstapplication, such as application X, and a similar stack would beavailable for application Y. Each of these stacks could be independentlyscrolled through using, for example, a gesture as discussed above.

FIG. 28 illustrates an exemplary method for managing screen displaycharacteristics according to another embodiment of this invention. Inaccordance with this embodiment, a determination is made whether anapplication can be maximized, and if it can be maximized, it is expandedto the dual screen mode or max mode, as appropriate, to substantiallyfill the display 1010 as illustrated in the figure. Here, applicationE1, which is an application that can be maximized, has been expandedusing the max mode to substantially or completely fill display 1010.

In FIG. 28, button 2618 allows a user to toggle between a single screenmode (as illustrated in FIG. 28) and an emulated dual screen mode, forexample, as illustrated in FIG. 26 and FIG. 27. Here, button 2618 doesnot include the “|” therefore indicating to the user the SP 1000 is insingle screen mode.

FIG. 29 illustrates an exemplary method of managing windows. In thisexemplary embodiment, and similar to the operation of the device 100,when the last application in the stack is moved to the side, the desktopis displayed. Even more specifically, as shown in FIG. 29, application F2908 is displayed in an upper portion of display 1010 and the desktop2912 is displayed in the lower portion of display 1010. Here the desktopis in focus, as illustrated by the focus indicator 2916. Thisconfiguration is available since the user has selected the dual-screenemulation mode button 2618.

FIG. 30 illustrates an exemplary method of displaying a keyboardaccording to one embodiment. In particular, when the SP is in portraitmode, the SP will have a keyboard area 3004 and an application area3008. Upon display of the keyboard 3004, the application in applicationarea 3008 is resized to substantially or completely fill the area of thescreen not occupied by the keyboard 3004.

FIG. 31A and FIG. 31B illustrate desktop availability in both the singleapplication mode and dual application mode in both the SP landscape modeand SP portrait mode. In particular, and in accordance with an exemplaryembodiment, the desktop 3104 will occupy the entirety of the screen1010. Additionally, and in accordance with this exemplary embodimentwhere the desktop is shown in a full-screen mode, the annunciator bar1312 can be expanded across the entirety of the screen 1010. This canoccur in both the portrait mode as shown in FIG. 31A as well as thelandscape mode as illustrated in FIG. 31B. From here, upon selection ofthe application launcher 3116, the application launcher can optionallyexpand across the entirety of the screen 1010 in either the portrait orlandscape mode. Similarly, the file explorer, which is launched bypressing the file explorer button 3120, can be similarly expanded intosubstantially all or all of the screen 1010 space.

FIG. 32A and FIG. 32B illustrate screen redrawing that may be requiredto transition the desktop from the device 100 to the SP 1000. Inparticular, in FIG. 32A, six exemplary desktop panels are shown3204-3224. These desktop panels are moveable in a carousel-like fashionbased on gesture input from a user. However, it may not be possible todirectly translate these panels to display correctly on the SP 1000without the panels being distorted or not occupying the entirety of thescreen 1010. Accordingly, in accordance with one exemplary embodiment,one or more of the panels 3204-3224 can be resized when displayed on theSP 1000 to accommodate all or substantially all of the screen 1010. Inaccordance with another exemplary embodiment, more than two of thepanels can be shown on the screen 1010, such as a portion of panel D23208, a portion of panel D3 3212 and a portion of panel D4 3216. In thismanner, the desktop illustrated on the SP 1000 will have a similarlook-and-feel to the desktop panels shown on device 100. The samecarousel-like motion is available via a gesture input to the SP 1000such that a user can scroll to the one or more panels of the desktop.

FIG. 33 illustrates an exemplary notifications display that behaves onthe SP 1000 in a very similar manner to that of the device 100. Inparticular, and whether in the portrait or landscape mode, notificationsand status/toggle buttons are provided that allow the user to, forexample, toggle on or off Bluetooth®, WiFi, screen lock, dual or singlescreen mode, power options, and the like. These, as well as otheroptions, are generally shown in area 3304. Additional notifications canalso be shown in area 3308 including one or more of carrier information,notification information, communication information, and the like asdiscussed above.

In more detail, area 3304 provides some buttons for standard widgetssuch as WiFi toggle on and off, Bluetooth® toggle on and off, and thelike. The screen lock toggle can allow, for example, user to lock thescreen thereby prohibiting it from rotating despite the orientation ofthe SP 1000. The toggle can change color or display characteristics toindicate whether screen lock has been enabled. The single/dualapplication mode button toggles, for example, three different statesincluding a dual application mode state, a single application modestate, and a single application lock state. The power mode toggletoggles between a handset optimized, SP optimized, hybrid powerconsumption, or of the like. These power modes can be associated withpower levels, as indicated by the two battery status indicators 3312 and3316 which correspond to the power levels in the device 100 and SP 1000,respectively.

FIG. 34A and FIG. 34B show exemplary methods of launching and displayingthe application launcher upon selection of the application launcherbutton 3116. In both the portrait mode illustrated in FIG. 34A andlandscape mode illustrated in 34B, and when the SP is in singleapplication mode, the application launcher can appear in a bubble so asto not necessarily take up the entirety of the screen 1010. However, forexample, upon receiving an appropriate gesture or input by the user, theapplication launcher can be expanded to take up the entirety of thescreen 1010. This could further be classified in a preference such thatthe default is to always open the application launcher in a bubble so asto not take up the entirety of the screen 1010, or to always open infull screen mode, taking up substantially all or all of the screen 1010.

FIG. 35A and FIG. 35B illustrate an optional embodiment whereby thesystem could provide “hints” as to the content of desktop panels thatare not fully in view. More specifically, FIG. 35A shows the firstembodiment of the desktop panels D1-D6, 3504-3524 respectively. Asdiscussed, a user is able to scroll through these panels in acarousel-type fashion, revealing any of the content in D1-D6. Inaccordance with the optional embodiment illustrated in FIG. 35B, wherethe same panels D1-D6 are available for viewing by user, the user isgiven a preview of one or more adjacent panels, here D2 3508 and D53520. In this configuration, this user is able to “peek” at the contentof the adjacent panel(s) without necessarily scrolling in a carousellike fashion to view the entirety of the panel. More specifically, theentirety of panel D3 3512 and D4 3516 is shown on the display 1010. Inaddition, approximately one third of panel D2 3508 and one third ofpanel D5 3520 are also shown on the display 1010. As will beappreciated, more or less of panels D2 and D5 could be shown, with thegreater of the panel being shown, the more visibility into that portionof the desktop the user would have.

FIG. 36 illustrates an optional embodiment for managing in a multipleapplication mode the stack of windows. This elegant method reinforcesthe conceptual model and assists the user with visualizing spatially the“carousel” type arrangement of the stack in the multi application mode.As is to be appreciated, while the exemplary embodiment shown in FIG. 36is directed toward portrait mode of SP1000, it can work equally well inthe landscape mode with the difference being instead of the carouselrotating from a top to bottom or bottom to top type arrangement, the“carousel” could be manipulated in a left to right or right to left typeoperation. However, the carousel could also work in a top to bottom orbottom to top mode in landscape mode as well.

In this exemplary embodiment, when multi-application mode is enabled viabutton 2618, application C 3604 and application D 3608 can be displayed,separated by separator 3612. In accordance with this optional exemplaryembodiment, there are also one or more overflow applications behindapplication C 3604, here the overflow applications being 3424 and 3428.In a similar manner, there can be one or more overflow applicationsbehind application D 3608, here application 3416 and application 3420.In this particular exemplary embodiment, the back and menu buttons 3432can be enabled with a portion of the desktop 3436 being viewable behindthe application stack. Upon receipt of one or more input gestures, suchas gesture 3440, a user can scroll through the “carousel” ofapplications, in this instance, relocating application D 3608 toapplication C 3604's position, and thereby revealing application 3416.In addition, the focus indicator can be displayed near the applicationthat is in focus. In this particular example, focus indicator 3444 isdisplayed beside application D. In accordance with an optional exemplaryembodiment, instead of the stack “stopping” when the user reaches thelast application, such as application 3420 or application 3428, theapplications can be stacked in a circular manner, and continuouslyrotate in response to one or more input gestures by a user.

These concepts can be extended to the situation where the keyboard isalso displayed in the multiple application mode. For example, and asillustrated in FIG. 37, the keyboard 3704 is displayed below theapplication stack 3708. “Behind” the application stack 3708, areadditional applications 3712 and 3716 that the user can access via, forexample, initiation of gesture 3720. This exemplary embodiment has theapplications scroll in a carousel-like fashion into and out of view,with the keyboard 3704 remaining visible, for example, at the bottom ofdisplay 1010. As with the embodiment in FIG. 35, the back and menubuttons can be enabled and, for example, virtually displayed on thedisplay 1010 as illustrated by graphical button 3724.

FIG. 38 outlines an exemplary method for docking the device 100 with thesmartpad 1000. In particular, control begins in step S3802 and continuesto step S3804. In step S3804 the insertion of the device into the SP isdetected. Next, in step S3806, power management can optionally begin.For example, and as discussed, the SP can be used as a power source forthe device, the device can be used as a power source for the SP, powercan be shared between the two devices and/or the SP can be plugged in,via for example, an AC adaptor, which is capable of charging one or moreof the SP and the device 100. Then, in step S3808, the display of thedevice 100 is optionally turned off to, for example, conserve power.Control then continues to step S3810. In step S3810, communicationand/or connectivity are established between the device 100 and the SP.Next, in step S3812, display and other input/output functions on the SPare enabled. Then, in step S3814, the device software settings aremapped to the smartpad hardware settings. Control then continues to stepS3816.

In step S3816, the screen orientation of the device is automaticallyaligned to the orientation of the SP. Next, in step S3818, the lastapplication in focus on the device remains in focus and is displayed onthe SP. Normal operation and interaction with the SP then continuesutilizing, for example, the same gestures as are usable with the device100. Control then continues to step S3820 where the control sequenceends.

FIG. 39 illustrates an exemplary method of application/displayorientation/reorientation. In particular, control begins in step S3900and continues to step S3902. In step S3902, the orientation of the SP isdetected. Next, in step S3904, the application orientation on the deviceis detected. Then, in step S3906, one or more displayed applications arereoriented to be in the same orientation as the SP. In addition, andbased on the need for reorientation, a re-drawing or re-sizing of theapplication can also occur with the application(s) being displayed onthe SP. Control then continues to step S3908 where the control sequenceends.

FIG. 40 outlines an exemplary method for managing the keyboard. Inparticular, control begins in step S4000 and continues to step S4002. Instep S4002, determination is made as to whether a keyboard request hasbeen detected. If a keyboard request has not been detected, controljumps back to step S4000 with control otherwise continuing to stepS4004. In step S4004, a determination is made as to the orientation ofthe SP. If the SP is in the landscape orientation, control jumps to stepS4010 with control otherwise continuing to step S4006 with the SP beingin the portrait orientation. In step S4006, the keyboard is displayed inthe portrait mode.

Next, in step S4008, a determination is made as to whether there hasbeen an orientation change. If there has been an orientation change,control jumps to step S4010 with control otherwise continuing to stepS4014.

In step S4010, the keyboard is displayed in the landscape mode. Next, instep S4012, a determination is made as to whether there has been achange in orientation of the SP. If there has been a change in theorientation, control jumps to step S4006 with control otherwisecontinuing to S4014.

In step S4014, a determination is made as to whether the keyboard shouldbe hidden. If the keyboard should be hidden, control continues to stepS4016 with control otherwise continuing back to step S4004.

In step S4016, the keyboard is hidden with control continuing to stepS4018 where the control sequence ends.

FIG. 41 illustrates an exemplary method for window management. Inparticular, control begins in step S4100 and continues to step S4102. Instep S4102 a gesture is detected. As will be appreciated, and similar tothe device 100, this gesture can be on the touch-sensitive display, in aconfigurable area, and/or in the gesture capture region(s). In stepS4104, gesture direction can also optionally be detected. Then, in stepS4106, the next application window can be brought into view, enabling,for example, a user to scroll through application window stack. Adetermination is then made as to whether another gesture has beendetected. If another gesture has been detected, control jumps back tostep S4104 with control otherwise continuing to step S4110.

FIG. 42 outlines an exemplary method for screen management. Inparticular, control begins in step S4200 and continues to step S4202. Instep S4202, multiple application mode is enabled via, for example,selection of a button or toggle. Next, in step S4204, a user isoptionally prompted to select which applications will be displayed. Inan alternative embodiment, two adjacent applications in the stack aredisplayed, with one of the applications being the application that iscurrently in focus. Then, in step S4206, the screen is split with thefirst portion of the screen displaying a first application and a secondportion of the screen displaying a second application. Next, in S4208,the application that was detected to be in focus is then highlighted onthe SP in step S4210. Control then continues to step S4212.

In step S4212, a determination is made as to whether a new applicationhas been brought into focus. If a new application has been brought intofocus, control jumps back to step S4210 where that application ishighlighted with an “in-focus” indicator. Otherwise, control continuesto step S4214 where the control sequence ends.

FIG. 43 outlines an exemplary method for windows management. Inparticular, control begins in step S4300 and continues to step S4302. Instep S4302, a determination is made as to whether the application can bemaximized. Next, in step S4304, if the application is maximizable,control jumps to step S4306 where the application is expanded to eitherthe dual screen mode or the max mode. Control then continues to stepS4308 where the control sequence ends.

FIG. 44 outlines an exemplary method for transitioning from anapplication window to the desktop. In particular, control begins in stepS4400 and continues to step S4402. In step S4402, the last applicationin the application window stack is detected. Next, in step S4404, agesture is detected, the gesture requesting a “next” window, however thecurrent window is the last application in the window stack. In thisscenario, in step S4406, the desktop is displayed in that there are nofurther windows to display in the application window stack. Control thencontinues to step S4408 where the control sequence ends.

FIG. 45 illustrates an exemplary method of emulating the multi-screendisplay of the device 100 on the SP1000. In particular, control beingsin step S4500 and continues to step S4502. In step S4502, the desktop isdisplayed on the SP. Next, in step S4504, the desktop is logicallydivided on the SP into, for example, two sections. Then in step S4506, afirst screen of the desktop is displayed in a first logical portion ofthe SP display. Then, in step S4508, a second screen of the desktop isdisplayed in a second logical portion of the SP display. Control thencontinues to step S4510.

In step S4510, carousel movement of the “panels” shown in the displaycan be initiated through user input, such as a gesture. Control thencontinues to step S4512 where the control sequence ends.

FIG. 46 outlines an exemplary method of displaying multiple “panels” ofthe desktop on the SP. In particular, control begins in step S4600 andcontinues to step S4602. In step S4602, a portion of the desktop isdisplayed on the SP. Next, in step S4604, the desktop is logicallydivided on the smartpad to accommodate multiple desktop “panels.” Then,in step S4608, the first screen or panel of the desktop is displayed inone logical portion of the SP display. Then, in step S4610, a secondscreen or panel of the desktop is displayed bridging a first and asecond logical portion of the SP display. Then, a third screen or panelof the desktop is displayed in the second logical portion of the SPdisplay. Control then continues to step S4614.

In step S4614 carousel movement of the panels can be affected by, forexample, an input of a gesture by the user. Control then continues tostep S4616 where the control sequence ends.

FIG. 47 outlines an exemplary method of displaying one or more portionsof the desktop. In particular, control begins in step S4700 andcontinues to step S4702. In step S4702, an access request to the desktopis detected. Next, in step S4704, at least one desktop panel isdisplayed. Then, in step S4706, at least one additional desktop panel ispartially displayed on the desktop. Control then continues to stepS4708.

In step S4708, and upon detection of a gesture, the partially displayedpanel can be completely displayed on the display of the SP. Control thencontinues to step S4710 where the control sequence ends.

FIG. 48 outlines an exemplary method of windows management in multipleapplication mode. In particular, control begins in step S4800 andcontinues to step S4802. In step S4802, multiple application mode isentered. Next, in step S4804, the windows stack is arranged with one ormore applications being partially visible behind a first application.Next, in step S4806, the stack can be arranged with one or moreapplications also partially being visible behind a second application.Then, in step S4808, and upon receiving an input gesture from a user,carousel-like scrolling can be enabled through the stack until the endof the stack is reached, or in a second embodiment, the stack can have a“circular” arrangement where continuous scrolling through the stack ispossible. Control then continues to step S4810 where the controlsequence ends.

The exemplary systems and methods of this disclosure have been describedin relation to a smartpad and interaction with the device. However, toavoid unnecessarily obscuring the present disclosure, the precedingdescription omits a number of known structures and devices. Thisomission is not to be construed as a limitation of the scopes of theclaims. Specific details are set forth to provide an understanding ofthe present disclosure. It should however be appreciated that thepresent disclosure may be practiced in a variety of ways beyond thespecific detail set forth herein.

For example, the smartpad could have multiple physical and/or logicalscreens/displays. Additionally, the smartpad could be used with one ormore input devices such as a stylus, mouse, or the like. Moreover, thesmartpad could be populated with a processor, memory, communicationsmeans and the like that would allow for stand-alone operation. Evenfurther, the smartpad could be associated or docked with other types ofcommunications devices such as a smartphone such that the smartpad couldbe used as a display and/or I/O interface therefore.

An embodiment of a method 4900 for executing an application, such as aphone application, is shown in FIG. 49. While a general order for thesteps of the method 4900 is shown in FIG. 49. Generally, the method 4900starts with a start operation 4904 and ends with an end operation 4940.The method 4900 can include more or fewer steps or can arrange the orderof the steps differently than those shown in FIG. 49. The method 4900can be executed as a set of computer-executable instructions executed bya computer system and encoded or stored on a computer readable medium.Hereinafter, the method 4900 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-48.

An application, such as a phone application, is executed, in step 4908.In embodiments, a processor 204 receives indication to execute anapplication through a user interface 110, 114, 112, 116, etc. Theindication can be a selection of an icon associated with theapplication. In other embodiments, the indication can be a signalgenerated from another application or event, such as receiving a phonecall or other communication, which causes the application to executeautomatically. The processor 204 can retrieve the application 564 a fromthe application store 560 and begin its execution. In executing theapplication 564 a, a user interface can be generated for a user, asdescribed in conjunction with FIGS. 50-61D.

In creating a user interface, the application 564 a can begin executingto create a manifest, in step 4912. A manifest is a data structure thatindicates the capabilities of the application 564 a. The manifest cangenerally be created from the resources in the resources directory ofthe application 564 a. The resources directory can indicate the types ofmodes, locations, or other indications for how the user interface shouldbe configured in the multi-display device 100. For example, the severalmodes can include: “classic mode” that indicates that the application564 a is capable of being displayed on a single screen or display110/114; “dual mode” that indicates that the application 564 a iscapable of being displaced on two or more displays 110 and 114; “maxmode” that indicates the application 564 a is capable of being displayedor desires to be displayed across multiple displays 110 and 114; and/or“bilateral mode” that indicates that the application 564 a is capable ofbeing displayed on 2 or more displays 110 and 114 when the device 100 isin easel mode (see FIGS. 1I and/or 1J).

Similarly, the manifest can include a desired or allowed location withinthe displays 110/114. The possible locations can include: “left”, whichindicates that the application 564 a desires to be displayed on the leftdisplay 110; “right”, which indicates that the application 564 a desiresto be displayed on the right display 114; and/or other indications ofwhere a location should be including possible “top” and/or “bottom” ofone or more of the displays 110/114.

The application 564 a can also indicate that it desires to be displayedin a “minimum” window, which is a window that occupies less than thefull area of a single display. There may be other modes possible for theapplication 564 a, which may be included in the manifest. The manifestcan be sent from the application 564 a to the multi-display managementmodule 524.

The multi-display management module 524 can receive the manifest, instep 4916. In receiving the manifest, the multi-display managementmodule 524 can use the information to determine a display binding forthe application 564 a. The manifest may be received more than once fromthe application 564 a based on changes in how the application 564 a isbeing executed, where the application 564 a desires to have a differentdisplay setting for the new mode. Thus, with the manifest, theapplication 564 a can indicate to the multi-display management module524 how best to or what is the desired for the application's userinterface. The multi-display management module 524 can use theinformation in the manifest to determine the best fit for the userinterface depending on how the device 100 is currently configured.

The multi-display management module 524 can determine the applicationdisplay mode, in step 4920. Here the multi-display management module 524receives or retrieves an indication of the device 100 configuration. Forexample, the multi-display management module 524 can determine if thedevice is in single display configuration (see FIG. 6A, 6B, 6D, or 6E),dual display configuration (see FIG. 6C or 6F), bilateral displayconfiguration (see FIG. 6G or 6H), or one of the other displayconfigurations (see FIG. 6I or 6J).

Further, the multi-display management module 524 can determine if thedevice 100 is in a portrait or landscape orientation. With thisinformation, the multi-display management module 524 may then considerthe capabilities or preferences listed for the application 564 a in thereceived manifest. The combined information may then allow themulti-display management module 524 to determine a display binding. Thedisplay binding can include which of the one or more displays 110 and/or114 are going to be used to display the application's user interface(s).For example, the multi-display management module 524 can determine thatthe primary display 110, the secondary display 114, or all displays 110and 114 of the device 100 will be used to display the application's userinterface.

The display modes setting can be assigned by creating or setting anumber in the display binding. This number can be “0” for the primarydisplay 110, “1” for the secondary display 114, or “2” for dual displays110 and 114. The display mode setting can also indicate if theapplication 564 a should display the user interface in portrait orlandscape orientation. Further, there may be other settings, forexample, providing a max mode or other setting that may indicate how theapplication 564 a is to be displayed on the device. The display bindinginformation is stored in a data structure to create and set a binding,in step 4924.

The established display binding may then be provided, by themulti-display management module 524, to the application 564 a, in step4928. The provided display binding data structure can become anattribute of the application 564 a. An application 564 a maythereinafter store the display binding attribute in the memory of thedevice 100. The application 564 a with the display binding may thengenerate a user interface based on this display binding. The application564 a may be unaware of the position of the display 110/114 but may beable to determine, from the display binding, the size of the availableuser interface to generate a window that has particular characteristicsfor that display setting.

When a configuration change happens to the device 100, the multi-displaymanagement module 524 may change the display binding and send a newdisplay binding to the application 564 a. In embodiments, themulti-display management module 524 may indicate to the application 564a that there is a new binding or, in other embodiments, the application564 a may request a display configuration change or a new displaybinding, in which case the multi-display management module 524 may senda new display binding to the application 564 a. Thus, the multi-displaymanagement module 524 can change the configuration of the display forthe application 564 a by altering the display binding for theapplication 564 a during the execution of that application 564 a.

The multi-display management module 524 thereinafter, while theapplication 564 a is executing, can determine if there has been aconfiguration change to the device 100, in step 4932. The configurationchange may be an event (see FIGS. 3A and 3B) triggered by one or moresignals from one or more hardware sensor 172, 176, etc. For example, ifthe device 100 is changed from portrait 304 to landscape 340orientation, Hall effect sensors 172 may indicate to the framework 520that a display configuration change has been made. Other changes mayinclude transitions from a single display 304 to a dual displayconfiguration 320, by opening the device. Other types of configurationchanges may be possible and may be signaled to alert the multi-displaymanagement module 524 of the configuration change. If a configurationchange has been made, the method 4900 proceeds YES to step 4920 so thatthe multi-display management module 524 can determine new applicationdisplay mode settings and create a new display binding, which may bepassed to the application 564 a. If there are no configuration changes,the method 4900 precedes NO to step 4936.

In step 4936, a new application mode change may be determined.Application mode changes can also occur in the application 564 a, andthus, the application 564 a can determine if something has occurredwithin the application 564 a that requires a different display setting.Modes are described hereinafter with respect to FIG. 51. The mode changecan create a desire to change the display 110/114, and thus, require theapplication 564 a to generate a new manifest. If the application 564 adoes sense a mode change or an event has occurred that requires a changein display setting, the method 4900 proceeds YES back to step 4912. Atstep 4912, a new manifest or preference is created by the application564 a that may be received by the multi-display management module 524 todetermine if the multi-display management module 524 can change thedisplay binding. If it is possible to provide the preferred display, themulti-display management module 524 can create a new display binding andsend display binding back to the application 564 a and allow theapplication 564 a to alter its user interface. If no mode change issensed or an event is not received to create a mode change, the method4900 proceeds NO to end operation 4940.

One of the applications that may be executed by the device is a phoneapplication. The phone application can have a user interface 5000 thathas a particular structure as described in FIG. 50. Here, the userinterface 5000 may have one or more portions that can be standard or maybe generalized across all displays generated by the phone application.The portions may include an annunciator bar 5004, a header bar 5008, anumber display field 5012, a content area 5016, and/or an action menubar 5020. Each of these different portions are described hereinafter.

The annunciator bar 5004 is a portion of the user interface 5000 thatmay display one or more system settings. For example, the annunciatorbar 5004 can include a current time, a power level, one or moreindications of what networks may be available to communicate over (suchas Bluetooth, a cell network, an 802.50 network, etc.), or otherindications of system settings. This information may be displayed asicons or other types of user interface devices in the annunciator bar5000.

The header bar 5008 can indicate what the specific user interface isbeing displayed. For example, the header bar 5008 can include text thatsays “Phone”, “Call Log”, “Contacts,” “Favorites,” or other informationto indicate what type of user interface is being displayed. The headerbar 5008 allows the user to determine quickly the status or mode of thephone application and understand the context of the information beingdisplayed in other portions of the user interface 5000.

The number display field 5012 can provide one or more editable fieldsthat allow the user to enter a phone number or to interact withapplication data in a manner that best suits the user. For example, thenumber display field 5012, for a dialer, can present a phone number ofan in-coming call, an out-going call, or of a contact from the contactsor call log. Thus, the number display field 5012 allows the user tointeract with the phone user interface 5000.

The content area 5016 can provide one or more user-specific items ofinformation. For example, in the dialer mode, the content area 5016 candisplay a set of numbers that may be selected by the user to enter aphone number to dial. There may be other information displayed in thecontent area 5016 that that shown in FIG. 50, and the information may beorganized differently depending upon what the phone application is doingor what service the phone application is providing at the time.

The action menu bar 5020 can provide one or more user-selectable devicesthat allow the user to change the phone application operation or systemoperation. For example, the action menu bar can 5020 include an undoselection, a compose selection, a read all selection, or some otherdevice that changes or causes the phone application to execute anoperation. These user selectable devices in the action menu bar 5020 canhave more global effect than those selectable devices described in thetext tab bar, which may only affect the information within the contentarea 5016. Hereinafter, the phone application user interfaces will bedescribed in conjunction with the different modes possible within thephone application. These different modes may change the look and feel ofthe user interface for the phone application. However, these differentuser interface layouts generally follow the structures described in FIG.50.

A phone application is capable of several different application modes asshown in FIG. 51. The diagram 5100 displays at least some of thedifferent possible modes and sub-modes within a phone application. Thegeneral modes that exist at the top tier of the diagram 5100 aredescribed hereinafter, however the sub-modes may not be describedbecause those sub-modes may be self-evident, by the information in thediagram, or may create user interfaces which shall be shown hereinafterbut described only in relation to the general modes.

An in-call mode 5104 generally is an application mode that exists whenthe user is engaged in or is making a phone call. The in-call mode 5104can be accessed through out-going calls from other modes or directly.Further, the in-call mode 5104 can occur automatically upon receipt ofan in-coming call. While a call is active, the phone application 5100remains in the in-call mode 5104.

The dialer mode 5108 allows the user to dial a phone number to make acall. This mode can present a set of numbers to dial (representing anumber pad). The user can select numbers to enter a phone number. Uponselecting a “call” device, the phone application 5100 can place anoutgoing call and enter the in-call mode 5104.

The call log mode 5112 provides information to the user about previousphone calls or voicemails. For example, the call log can storeinformation about the called person, the time, the date, a voicemail, orother information associated with a phone call. At a later time, theuser can access this stored information. Further, the call log canmaintain like information as a group. Thus, calls from the same personmay be presented to the user as a set. The call log mode 5112 may alsoallow the user to manage files and folders within the call log, forexample, adding, deleting, renaming, or changing the display of loggedcalls. These folders can be displayed in the call log to allow the userto better manage the different call information.

The call log mode 5112 may have sub-modes for sorting the display of theprevious phone calls, for example, the call detail mode shows details ofa group or a single phone call. The call log mode 5112 may also have a“by sender” sub-mode, which can display the phone calls, in the calllog, by the sender in alphabetical order. Further, the call log mode5112 can have a “voicemail” sub-mode, which can display the phone callsby the phone calls that were received as voicemails. The call log mode5112 can also allow the user to manage the call log by editing a list,moving calls into folders, deleting phone calls, or doing othermanagerial tasks with the emails in the call log.

A contacts mode 5116 allows the user to search, edit, add to, deletefrom, contacts in a contacts list. Thus, the user may select one or morecontacts, within the contacts list, which may transition the phoneapplication to the call log mode 5112. Within the contacts mode 5116,the user may be able to call a contact. Thus, the user is able tointeract with the content of a contacts list within the contacts mode5116.

A favorites mode 5120 allows the user to search phone numbers that aremost often received and/or most often called. The favorites mode 5120may allow the user to select the contact to call, add the favorite tothe contacts, view call log information for the favorite, etc. Thesetasks may be conducted within the user interface generated by thefavorites mode 5120. Each of these different modes may have userinterfaces to provide information to the user. These different modes maybe transitioned between each other and thus cause the user interface tochange.

In embodiments, the user interface mode may change depending on theapplication mode. Thus, the phone application may require, for example,a classic user interface mode when in dialer mode 5104 but require adual display or max mode in call log mode 5112. Thus, by changing theapplication mode, the application may desire a new user interface, whichrequires the application to send a new manifest to the multi-displaymanagement module 524. These transitions are as described in conjunctionwith FIG. 49, and the display changes may be described in the variousfigures provided hereinafter. Thus, the application is able totransition between different displays based on the application mode thuschanging which type of displays will be seen as described in the figuresthat are presented hereinafter. Further, depending on the displayconfiguration (single display, dual display, bilateral display, etc.)each application mode may have different user interface configurations.These user configurations may also be shown in the figures that proceedhereinafter. The application can transition between different userinterfaces even when in the same application modes when the device 100changes its configuration.

The figures described hereinafter, i.e., FIGS. 52A through 59B, arearranged similarly. Each set of figures, e.g., FIGS. 52A-52F, 53A-53F,etc., represent user interfaces for different device configurations butthe same application mode. Thus, it is possible to understand how theuser interface will change in a single application mode when the deviceconfiguration changes. Thus, the following figures demonstrate how thephone application displays content based on the device state and theapplication mode. Transitions between phone application user interfacesmay be as described in conjunction with FIG. 49.

FIGS. 52A-52F show the user interfaces for the dialer mode 5104. Userinterface 5204 may be displayed when the device 100 is in the closed,portrait configuration (as described in conjunction with FIGS. 6A and/or6B). The user interface 5204 may also occupy a single screen in aportrait, dual-display configuration (as described in conjunction withFIG. 6C), as shown in FIG. 52A. User interface 5208 and 5212 may bedisplayed when the device 100 is in the portrait, dual-displayconfiguration (as described in conjunction with FIG. 6C). Whentransitioning between the dual-display configurations shown in FIGS. 52Aand 52B, a new child window 5212 may be opened, the window 5208 mayremain in the primary screen 104 and the other window 5212 generated forthe second screen 108. To transition between the two configurations, auser may execute a drag 400 or a flick 404, as described in conjunctionwith FIGS. 4C and 4D, respectively. The drag 400 or flick 404 may beconducted in an off-screen gesture area 120 of the primary screen 104.

If another user action is received, user interface 5204 may be moved tothe second screen 108, as shown in FIG. 52C. Again, the user action maybe a drag 400 or flick 404 conducted in an off-screen gesture area 120of the primary screen 104. The action may reveal the desktop 5212, asshown in FIG. 52C. In FIGS. 52D through 52 F, the user may conduct adrag 400 or flick 404 conducted in an off-screen gesture area 124 of thesecondary screen 108. Thus, a dialer window 5204 shown in the secondaryscreen 108 is moved to the primary screen 104 and a child window 5208 isgenerated in the secondary screen 108, as shown in FIG. 52E. A furtherdrag 400 or flick 404 conducted in an off-screen gesture area 124 of thesecondary screen 108 will hide the child window 5208 and reveal thedesktop in the secondary screen 108, as shown in FIG. 52F.

FIGS. 53A-53H show the user interfaces for the dialer mode 5104 in thelandscape, dual-display configuration. (as described in conjunction withFIG. 6F). The user interface 5304 may occupy a single screen 104 in alandscape, dual-display configuration, as shown in FIG. 53A. Userinterface 5304 and 5308 may be displayed when the device 100 is in thelandscape, dual-display configuration (as described in conjunction withFIG. 6F). When transitioning between the dual-display configurationsshown in FIGS. 53A and 53B, a child window 5308 may be closed, thewindow 5304 may shift from the secondary screen 108 to the primaryscreen 104. To transition between the two configurations, a user mayexecute a drag 400 or a flick 404, as described in conjunction withFIGS. 4C and 4D, respectively. The drag 400 or flick 404 may beconducted in an off-screen gesture area 124 of the secondary screen 108.

In another embodiment, the user interface 5304 may occupy a singlescreen 108 in a landscape, dual-display configuration, as shown in FIG.53C. User interface 5304 and 5308 may be displayed when the device 100is in the landscape, dual-display configuration (as described inconjunction with FIG. 6F). When transitioning between the dual-displayconfigurations shown in FIGS. 53C and 53D, a child window 5308 may beclosed, the window 5304 may remain displayed on screen 108 while adesktop 5312 is displayed or revealed on the primary screen 104. Totransition between the two configurations, a user may execute a drag 400or a flick 404, as described in conjunction with FIGS. 4C and 4D,respectively. The drag 400 or flick 404 may be conducted in anoff-screen gesture area 124 of the secondary screen 108.

In still another embodiment, the user interface 5304 may occupy a singlescreen 104 in a landscape, dual-display configuration, as shown in FIG.53E. User interface 5304 and 5308 may be displayed when the device 100is in the landscape, dual-display configuration (as described inconjunction with FIG. 6F). When transitioning between the dual-displayconfigurations shown in FIGS. 53E and 53F, a child window 5308 may beclosed, the window 5304 may be moved to the secondary screen 108, whilea desktop 5312 is displayed or revealed on the primary screen 104. Totransition between the two configurations, a user may execute a drag 400or a flick 404, as described in conjunction with FIGS. 4C and 4D,respectively. The drag 400 or flick 404 may be conducted in anoff-screen gesture area 124 of the secondary screen 108.

In yet another embodiment, the user interface 5304 may occupy a singlescreen 104 in a landscape, dual-display configuration, as shown in FIG.53G. User interface 5304 and 5308 may be displayed when the device 100is in the landscape, dual-display configuration (as described inconjunction with FIG. 6F). When transitioning between the dual-displayconfigurations shown in FIGS. 53G and 53H, a child window 5308 may beclosed, the window 5304 may remain displayed on screen 104, while adesktop 5312 is displayed or revealed on the secondary screen 108. Totransition between the two configurations, a user may execute a drag 400or a flick 404, as described in conjunction with FIGS. 4C and 4D,respectively. The drag 400 or flick 404 may be conducted in anoff-screen gesture area 124 of the secondary screen 108.

FIGS. 54A-54E show the user interfaces for the call log mode 5112. Userinterface 5404 may be displayed when the device 100 is in the closed,portrait configuration (as described in conjunction with FIGS. 6A and/or6B). The user interface 5404 may also occupy a single screen in aportrait, dual-display configuration (as described in conjunction withFIG. 6C), as shown in FIG. 54A. User interface 5404 and 5408 may bedisplayed when the device 100 is in the portrait, dual-displayconfiguration (as described in conjunction with FIG. 6C), as shown inFIG. 54B. When transitioning between the dual-display configurationsshown in FIGS. 54A and 54B, a new child window 5408 may be opened, thewindow 5408 may remain in the primary screen 104 and the other window5408 generated for the second screen 108. The child window 5408 may showcall log information associated with the person selected in the window5404. To transition between the two configurations, a user may execute adrag 400 or a flick 404, as described in conjunction with FIGS. 4C and4D, respectively. The drag 400 or flick 404 may be conducted in anoff-screen gesture area 120 of the primary screen 104.

If another user action is received, user interface 5404 may be moved tothe second screen 108, as shown in FIG. 54C. Again, the user action maybe a drag 400 or flick 404 conducted in an off-screen gesture area 120of the primary screen 104. The action may reveal the desktop 5412, asshown in FIG. 54C. In FIGS. 54D through 54 F, the user may conduct adrag 400 or flick 404 conducted in an off-screen gesture area 124 of thesecondary screen 108. Thus, a call log window 5404 shown in thesecondary screen 108 is moved to the primary screen 104 and a childwindow 5408 is generated in the secondary screen 108, as shown in FIG.54E. A further drag 400 or flick 404 conducted in an off-screen gesturearea 124 of the secondary screen 108 will hide the child window 5408 andreveal the desktop in the secondary screen 108, as shown in FIG. 54F.

In another embodiment, FIGS. 55A-55E show the user interfaces foranother sub-mode of the call log mode 5112. User interface 5504 may bedisplayed when the device 100 is in the closed, portrait configuration(as described in conjunction with FIGS. 6A and/or 6B). The userinterface 5504 may also occupy a single screen in a portrait,dual-display configuration (as described in conjunction with FIG. 6C),as shown in FIG. 55A. User interface 5504 and 5508 may be displayed whenthe device 100 is in the portrait, dual-display configuration (asdescribed in conjunction with FIG. 6C), as shown in FIG. 55B. Whentransitioning between the dual-display configurations shown in FIGS. 55Aand 55B, a new child window 5508 may be opened, the window 5508 mayremain in the primary screen 104 and the other window 5508 generated forthe second screen 108. The child window 5508 may show call detailinformation associated with a single call from a person selected in thewindow 5504. To transition between the two configurations, a user mayexecute a drag 400 or a flick 404, as described in conjunction withFIGS. 4C and 4D, respectively. The drag 400 or flick 404 may beconducted in an off-screen gesture area 120 of the primary screen 104.

If another user action is received, user interface 5504 may be moved tothe second screen 108, as shown in FIG. 55C. Again, the user action maybe a drag 400 or flick 404 conducted in an off-screen gesture area 120of the primary screen 104. The action may reveal the desktop 5512, asshown in FIG. 55C. In FIGS. 55D through 55 F, the user may conduct adrag 400 or flick 404 conducted in an off-screen gesture area 124 of thesecondary screen 108. Thus, a call log window 5504 shown in thesecondary screen 108 is moved to the primary screen 104 and a childwindow 5508 is generated in the secondary screen 108, as shown in FIG.55E. A further drag 400 or flick 404 conducted in an off-screen gesturearea 124 of the secondary screen 108 will hide the child window 5508 andreveal the desktop in the secondary screen 108, as shown in FIG. 55F.

FIGS. 56A-56F show the user interfaces for the dialer mode 5108. Theuser interface 5604 may be displayed when the device 100 is in theclosed, portrait configuration (as described in conjunction with FIGS.6A and/or 6B). However, as shown in FIG. 56A, user interface 5604 and5608 may be displayed when the device 100 is in the portrait,dual-display configuration (as described in conjunction with FIG. 6C).When transitioning to the landscape, dual-display configuration (asdescribed in conjunction with FIG. 6F), the windows 5604 and 5608 mayremain displayed on the same screens, i.e., window 5604 is displayed onscreen 104 and window 5608 is displayed on screen 108. However, thewindows 5604 and 5608 switch to a landscape view as shown in FIG. 56B.The switch to the landscape configuration can be made through thecounterclockwise rotation of the device 100, as represented by the arrow5612. The device 100 may be reconfigured by rotating the deviceclockwise, as represented by arrow 5616. Here, the windows 5604 and 5608again remain displayed on the same screens 104 and 108, but are againdisplayed in portrait configuration, as shown in FIG. 56C.

As shown in FIG. 56D, user interface 5604 and 5608 may be displayed whenthe device 100 is in the portrait, dual-display configuration (asdescribed in conjunction with FIG. 6C). When transitioning to thelandscape, dual-display configuration (as described in conjunction withFIG. 6F), the windows 5704 and 5708 may change the screens upon whichthe windows 5604 and 5608 are displayed, i.e., window 5604 is displayedon screen 108 and window 5608 is displayed on screen 104. Further, thewindows 5604 and 5608 switch to a landscape view as shown in FIG. 56E.Thus, the dialer window 5604 remains at the bottom of the view presentedto the user. The switch to the landscape configuration can be madethrough the clockwise rotation of the device 100, as represented by thearrow 5620. The device 100 may be reconfigured by rotating the devicecounterclockwise, as represented by arrow 5624. Here, the windows 5604and 5608 return to screens 104 and 108, respectively and are againdisplayed in portrait configuration, as shown in FIG. 56F.

FIGS. 57A-57F show the user interfaces for the call log mode 5112. Theuser interface 5704 may be displayed when the device 100 is in theclosed, portrait configuration (as described in conjunction with FIGS.6A and/or 6B). However, as shown in FIG. 57A, user interface 5704 and5708 may be displayed when the device 100 is in the portrait,dual-display configuration (as described in conjunction with FIG. 6C).When transitioning to the landscape, dual-display configuration (asdescribed in conjunction with FIG. 6F), the windows 5708 may expand andbe displayed over both screens 104 and 108. Thus, the child window 5708,showing details about the call log completes a “gravity drop” andexpands to fill the available display space, as shown in FIG. 57B. Theswitch to the landscape configuration can be made through thecounterclockwise rotation of the device 100, as represented by the arrow5712. The device 100 may be reconfigured by rotating the deviceclockwise, as represented by arrow 5716. Here, the windows 5704 and 5708again are displayed on the same screens 104 and 108 as in FIG. 57A.Thus, the child window 5708 shrinks to be displayed in one screen 108and the window 5704 is again displayed in the primary screen 104, asshown in FIG. 57C.

As shown in FIG. 57D, user interface 5704 and 5708 may be displayed whenthe device 100 is in the portrait, dual-display configuration (asdescribed in conjunction with FIG. 6C). When transitioning to thelandscape, dual-display configuration (as described in conjunction withFIG. 6F), the child window 5708 may expand from occupying screen 108 tofilling both screens 104 and 108. Further, the window 5708 switches to alandscape view as shown in FIG. 57E. Thus, the call log detail window5708 changes location to the top of the view presented to the user. Theswitch to the landscape configuration can be made through the clockwiserotation of the device 100, as represented by the arrow 5720. The device100 may be reconfigured by rotating the device 100 counterclockwise, asrepresented by arrow 5724. Here, the windows 5704 and 5708 return toscreens 104 and 108, respectively and are again displayed in portraitconfiguration, as shown in FIG. 57F. Further, window 5708 shrinks tofill only screen 108.

In another embodiment, FIGS. 58A-58B show the user interface for thein-call mode 5104. User interface 5804 may be displayed when the device100 is in the closed, portrait configuration (as described inconjunction with FIGS. 6A and/or 6B). The user interface 5804 may alsooccupy a single screen 104 in a portrait, dual-display configuration (asdescribed in conjunction with FIG. 6C), as shown in FIG. 58A. Userinterface 5804 may be displayed when the device 100 is in the portrait,dual-display configuration (as described in conjunction with FIG. 6C),as shown in FIG. 58B, in another window 108. When transitioning betweenthe dual-display configurations shown in FIGS. 58A and 58B, the window5804 moves between screens 104 and 108. A desktop 5812 is shown in theother screen 104 or 108 as the in-call mode 5104 does not have a childwindow to present. To transition between the two configurations, a usermay execute a drag 400 or a flick 404, as described in conjunction withFIGS. 4C and 4D, respectively. The drag 400 or flick 404 may beconducted in an off-screen gesture area 120 of the primary screen 104.

FIGS. 59A-B show the user interfaces for the call log mode 5112 but asshown on the smartpad 5900. It should be noted that all user interfacetransitions shown with respect to FIGS. 52A-58B can also be displayed orprovided on the smartpad 5900, although the formatting may be differentin minor respects. It should also be noted that although the smartpad5900 is a single screen device, the smartpad 5900 can display two ormore virtual displays as shown in FIG. 59A. User interface 5904 maydisplay windows 5908 and 5912 when the smartpad 5900 is in the landscapeconfiguration. User interface 5912 may be displayed when the smartpad5900 is in the portrait configuration, as shown in FIG. 59B. Whentransitioning to different configurations, a new child window may beopened, the window 5912 may expand across both displays, a keyboard mayexpand across both virtual displays, or the window 5908/5912 may remainin the set virtual display, and other content from another applicationor the desktop may be shown in the other virtual display.

FIGS. 60A-60G show the user interface 6000 for the active call screen6004 in the landscape, dual-display configuration. (as described inconjunction with FIG. 6F). The user interface 6004 may occupy a singlescreen 108 in a landscape, dual-display configuration, as shown in FIG.60A. User interface 6004 and 6008 may be displayed when the device 100is in the landscape, dual-display configuration (as described inconjunction with FIG. 6F). When in the active call mode, it is possibleto shift the active call window to reveal the desktop 6008 or otherwindow. Thus, if a gesture is received, the active call window may shiftfrom the secondary screen 108 to the primary screen 104, as shown inFIGS. 60A and 60B. To transition between the two configurations, a usermay execute a drag 400 or a flick 404, as described in conjunction withFIGS. 4C and 4D, respectively. The drag 400 or flick 404 may beconducted in an off-screen gesture area 120, 124 of the primary screen104 or the secondary screen 108.

In another embodiment, the user interface 6004 may occupy a singlescreen 108 in a landscape, dual-display configuration, as shown in FIG.60C. User interface 6004 and 6008 may be displayed when the device 100is in the landscape, dual-display configuration (as described inconjunction with FIG. 6F). When transitioning between the dual-displayconfigurations shown in FIGS. 60C and 60D, the window 6004 may shiftfrom the primary screen 104 to the secondary screen 108. To transitionbetween the two configurations, a user may execute a drag 400 or a flick404, as described in conjunction with FIGS. 4C and 4D, respectively. Thedrag 400 or flick 404 may be conducted in an off-screen gesture area120, 124 of the primary screen 104 or the secondary screen 108.

In still another embodiment, the user interface 6004 may occupy a singlescreen 108 in a landscape, dual-display configuration, as shown in FIG.60E. User interface 6004 and 6008 may be displayed when the device 100is in the landscape, dual-display configuration (as described inconjunction with FIG. 6F). When transitioning between the dual-displayconfigurations shown in FIGS. 60E and 60F, the window 6004 may be movedto the secondary screen 108, while a desktop 6008 is displayed orrevealed on the primary screen 104. To transition between the twoconfigurations, a user may execute a drag 400 or a flick 404, asdescribed in conjunction with FIGS. 4C and 4D, respectively. The drag400 or flick 404 may be conducted in an off-screen gesture area 120, 124of the primary screen 104 or the secondary screen 108.

In yet another embodiment, the user interface 6004 may occupy a singlescreen 108 in a landscape, dual-display configuration, as shown in FIG.60G. User interface 6004 and 6008 may be displayed when the device 100is in the landscape, dual-display configuration (as described inconjunction with FIG. 6F). When transitioning between the dual-displayconfigurations shown in FIGS. 60G and 60H, the window 6004 may shift tothe primary screen 104, while a desktop 6008 is displayed or revealed onthe secondary screen 108. To transition between the two configurations,a user may execute a drag 400 or a flick 404, as described inconjunction with FIGS. 4C and 4D, respectively. The drag 400 or flick404 may be conducted in an off-screen gesture area 120, 124 of theprimary screen 104 or the secondary screen 108.

Furthermore, while the exemplary aspects, embodiments, and/orconfigurations illustrated herein show the various components of thesystem collocated, certain components of the system can be locatedremotely, at distant portions of a distributed network, such as a LANand/or the Internet, or within a dedicated system. Thus, it should beappreciated, that the components of the system can be combined in to oneor more devices, such as a tablet-like device, or collocated on aparticular node of a distributed network, such as an analog and/ordigital telecommunications network, a packet-switch network, or acircuit-switched network. It will be appreciated from the precedingdescription, and for reasons of computational efficiency, that thecomponents of the system can be arranged at any location within adistributed network of components without affecting the operation of thesystem. For example, the various components can be located in a switchsuch as a PBX and media server, gateway, in one or more communicationsdevices, at one or more users' premises, or some combination thereof.Similarly, one or more functional portions of the system could bedistributed between a telecommunications device(s) and an associatedcomputing device.

Furthermore, it should be appreciated that the various links connectingthe elements can be wired or wireless links, or any combination thereof,or any other known or later developed element(s) that is capable ofsupplying and/or communicating data to and from the connected elements.These wired or wireless links can also be secure links and may becapable of communicating encrypted information. Transmission media usedas links, for example, can be any suitable carrier for electricalsignals, including coaxial cables, copper wire and fiber optics, and maytake the form of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Also, while the flowcharts have been discussed and illustrated inrelation to a particular sequence of events, it should be appreciatedthat changes, additions, and omissions to this sequence can occurwithout materially affecting the operation of the disclosed embodiments,configuration, and aspects.

In yet another embodiment, the systems and methods of this disclosurecan be implemented in conjunction with a special purpose computer, aprogrammed microprocessor or microcontroller and peripheral integratedcircuit element(s), an ASIC or other integrated circuit, a digitalsignal processor, a hard-wired electronic or logic circuit such asdiscrete element circuit, a programmable logic device or gate array suchas PLD, PLA, FPGA, PAL, special purpose computer, any comparable means,or the like. In general, any device(s) or means capable of implementingthe methodology illustrated herein can be used to implement the variousaspects of this disclosure. Exemplary hardware that can be used for thedisclosed embodiments, configurations and aspects includes computers,handheld devices, telephones (e.g., cellular, Internet enabled, digital,analog, hybrids, and others), and other hardware known in the art. Someof these devices include processors (e.g., a single or multiplemicroprocessors), memory, nonvolatile storage, input devices, and outputdevices. Furthermore, alternative software implementations including,but not limited to, distributed processing or component/objectdistributed processing, parallel processing, or virtual machineprocessing can also be constructed to implement the methods describedherein.

In yet another embodiment, the disclosed methods may be readilyimplemented in conjunction with software using object or object-orientedsoftware development environments that provide portable source code thatcan be used on a variety of computer or workstation platforms.Alternatively, the disclosed system may be implemented partially orfully in hardware using standard logic circuits or VLSI design. Whethersoftware or hardware is used to implement the systems in accordance withthis disclosure is dependent on the speed and/or efficiency requirementsof the system, the particular function, and the particular software orhardware systems or microprocessor or microcomputer systems beingutilized.

In yet another embodiment, the disclosed methods may be partiallyimplemented in software that can be stored on a storage medium, executedon programmed general-purpose computer with the cooperation of acontroller and memory, a special purpose computer, a microprocessor, orthe like. In these instances, the systems and methods of this disclosurecan be implemented as program embedded on personal computer such as anapplet, JAVA® or CGI script, as a resource residing on a server orcomputer workstation, as a routine embedded in a dedicated measurementsystem, system component, or the like. The system can also beimplemented by physically incorporating the system and/or method into asoftware and/or hardware system.

Although the present disclosure describes components and functionsimplemented in the aspects, embodiments, and/or configurations withreference to particular standards and protocols, the aspects,embodiments, and/or configurations are not limited to such standards andprotocols. Other similar standards and protocols not mentioned hereinare in existence and are considered to be included in the presentdisclosure. Moreover, the standards and protocols mentioned herein andother similar standards and protocols not mentioned herein areperiodically superseded by faster or more effective equivalents havingessentially the same functions. Such replacement standards and protocolshaving the same functions are considered equivalents included in thepresent disclosure.

The present disclosure, in various aspects, embodiments, and/orconfigurations, includes components, methods, processes, systems and/orapparatus substantially as depicted and described herein, includingvarious aspects, embodiments, configurations embodiments,subcombinations, and/or subsets thereof. Those of skill in the art willunderstand how to make and use the disclosed aspects, embodiments,and/or configurations after understanding the present disclosure. Thepresent disclosure, in various aspects, embodiments, and/orconfigurations, includes providing devices and processes in the absenceof items not depicted and/or described herein or in various aspects,embodiments, and/or configurations hereof, including in the absence ofsuch items as may have been used in previous devices or processes, e.g.,for improving performance, achieving ease and\or reducing cost ofimplementation.

The foregoing discussion has been presented for purposes of illustrationand description. The foregoing is not intended to limit the disclosureto the form or forms disclosed herein. In the foregoing DetailedDescription for example, various features of the disclosure are groupedtogether in one or more aspects, embodiments, and/or configurations forthe purpose of streamlining the disclosure. The features of the aspects,embodiments, and/or configurations of the disclosure may be combined inalternate aspects, embodiments, and/or configurations other than thosediscussed above. This method of disclosure is not to be interpreted asreflecting an intention that the claims require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive aspects lie in less than all features of a singleforegoing disclosed aspect, embodiment, and/or configuration. Thus, thefollowing claims are hereby incorporated into this Detailed Description,with each claim standing on its own as a separate preferred embodimentof the disclosure.

Moreover, though the description has included description of one or moreaspects, embodiments, and/or configurations and certain variations andmodifications, other variations, combinations, and modifications arewithin the scope of the disclosure, e.g., as may be within the skill andknowledge of those in the art, after understanding the presentdisclosure. It is intended to obtain rights which include alternativeaspects, embodiments, and/or configurations to the extent permitted,including alternate, interchangeable and/or equivalent structures,functions, ranges or steps to those claimed, whether or not suchalternate, interchangeable and/or equivalent structures, functions,ranges or steps are disclosed herein, and without intending to publiclydedicate any patentable subject matter.

What is claimed is:
 1. A method, comprising: providing a device havingat least first and second screens, the first and second screensincluding a touch sensitive display and each including a gesture capturearea separate from each respective touch sensitive display, each gesturecapture area adapted to receive an input, each gesture capture areahaving limited display capabilities relative to the touch sensitivedisplays and each capable of recognizing one or more gestures, whereinthe device executes a phone application, and wherein the phoneapplication is in an in-call mode; in a first display mode, presenting afirst user interface for the phone application on a first screen,wherein the first display mode includes displaying content in alandscape orientation and displaying content on the first screen;receiving input from a user only on at least one of the first and secondgesture capture areas associated with the first screen and the secondscreen, respectively, wherein the input is at least one of a pinch and aspread on at least one of the first and the second gesture captureareas, wherein the input includes a change in the display for the phoneapplication; determining a second display mode, wherein the seconddisplay mode includes displaying content in a portrait orientation anddisplaying content on the second screen; and in response to the inputand the determination that the device is in a second display mode,presenting the first user interface on the second screen; wherein eachof the first and second screens are configured to display at leastcontent in a first display mode and a second display mode, wherein thedevice is configured to simultaneously display a first display mode onthe first screen and a second display mode on the second screen, whereinthe first display and the second display are of different displayorientations that are independent of one another and do not display asingle continuous image across the first and second display screens,wherein the device is further configured to simultaneously display afirst content in a landscape orientation on the first screen and displaya second content in a portrait orientation on the second screen, andwherein the first and the second content read to a user at 90 degrees toone another.
 2. The method of claim 1, wherein in the first userinterface presents the same content on the first or second screen. 3.The method of claim 2, wherein a desktop is presented on the secondscreen in the first display mode.
 4. The method of claim 3, wherein thephone application remains in a single application mode during the changein the display for the user.
 5. The method of claim 4, wherein the phoneapplication is in a first application mode of two or more applicationmodes.
 6. The method of claim 5, wherein, in the in-call mode, thedevice is conducting an outgoing call, and in-coming call, or apreviously made call.
 7. The method of claim 1, further comprising:executing the phone application; receiving a manifest; setting a displaybinding for the phone application based on the first display mode; andproviding the display binding to the phone application.
 8. The method ofclaim 7, further comprising: setting a second display binding inresponse to the input; and providing the second display binding to thephone application to present the first user interface in the secondscreen.
 9. A device, comprising: a first screen, the first screenincluding a touch sensitive display area and a separate gesture capturearea adapted to receive an input and recognize one or more gestures, thefirst screen gesture capture area having limited display capabilitiesrelative to the first screen touch sensitive display area; a secondscreen, the second screen including a touch sensitive display area and aseparate gesture capture area adapted to receive an input and recognizeone or more gestures, the second screen gesture capture area havinglimited display capabilities relative to the second screen touchsensitive display area, wherein in a first display mode the first screendisplays an in-call user interface, in a landscape orientation, and thesecond screen displays a desktop; a memory; a processor, the processorcapable of receiving input from a user only on at least one of the firstand second screen gesture capture areas associated with the first screenand the second screen, respectively, wherein the input is at least oneof a pinch and a spread on the at least one of the first and the secondscreen gesture capture areas; a phone application program stored in thememory and executed by the processor, wherein the phone application isin an in-call mode, and wherein the application programming is operableto: send a manifest to a multi-display management module, the manifestproviding a preferred display mode; receive a display binding, thedisplay binding providing a first display mode; and present the firstuser interface in the first display mode; wherein each of the first andsecond screens are configured to display at least content in a firstdisplay mode and a second display mode, wherein the device is configuredto simultaneously display a first display mode on the first screen and asecond display mode on the second screen, wherein the first display andthe second display are of different display orientations that areindependent of one another and do not display a single continuous imageacross the first and second display screens, wherein the device isfurther configured to simultaneously display a first content in alandscape orientation on the first screen and display a second contentin a portrait orientation on the second screen, and wherein the firstand the second content read to a user at 90 degrees to one another. 10.The device of claim 9, wherein the processor in response to the, pinchor spread sends a second display binding to the phone application, andwherein the phone application program is further operable to: receivethe second display binding, the second display binding providing asecond display mode; and present a first user interface in a secondscreen while in the second display mode.
 11. The device of claim 9,further comprising: the phone application program further operable to:receive an input for the phone application program; in response to theinput, send a second manifest to the multi-display management module,the second manifest providing a second preferred display mode; andreceive a second display binding, the second display binding providingthe first display mode; and present only the first user interface in thefirst display mode, wherein the first user interface is provided on thefirst screen.
 12. The device of claim 9, further comprising amulti-display management module operable to: receive the manifest;determine a display mode; create the display binding; and send thedisplay binding to the phone application program.
 13. The device ofclaim 12, wherein the first display mode is a dual display mode inlandscape orientation with the first screen displays a window for thephone application, and wherein the second display mode is a dual displaymode in landscape orientation with the second screen displays the windowfor the phone application.
 14. A non-transitory computer readable mediumhaving stored thereon computer-executable instructions, the computerexecutable instructions causing a processor to execute a method forproviding a user interface for a phone application, thecomputer-executable instructions comprising: instructions to execute thephone application, wherein the phone application is in an in-call mode;instructions to generate a manifest for the phone application, whereinthe manifest provides a preferred display mode for the phoneapplication; instructions to receive the manifest; instructions todetermine a configuration for a device, wherein the configuration isopen with at least two screens visible by a user and in landscapeorientation; instructions to determine a first display mode for thedevice; instructions to create a display binding for the phoneapplication; instructions to send the display binding to the phoneapplication; and in response to determining the first display mode andreceiving the display binding; instructions to generate a first userinterface for a first screen and a desktop for the second screen;instructions to receive input from a user only on at least one of afirst and a second gesture capture area associated with the first screenand the second screen, respectively, wherein the input is at least oneof a pinch and a spread on the first and the second gesture captureareas; in response to receiving one of the pinch or spread, instructionsto switch to a second display mode; wherein each of the first and secondgesture capture areas have limited display capabilities relative to thefirst screen and the second screen, respectively; wherein each of thefirst and second screens are configured to display at least content in afirst display mode and a second display mode, wherein the device isconfigured to simultaneously display a first display mode on the firstscreen and a second display mode on the second screen, wherein the firstdisplay and the second display are of different display orientationsthat are independent of one another and do not display a singlecontinuous image across the first and second display screens, whereinthe device is further configured to simultaneously display a firstcontent in a landscape orientation on the first screen and display asecond content in a portrait orientation on the second screen, andwherein the first and the second content read to a user at 90 degrees toone another.
 15. The non-transitory computer readable medium of claim14, further comprising; in response to switching to the second displaymode, instructions to create a second display binding; instructions toreceive the second display binding; and instructions to present thefirst user interface on the second screen.
 16. The non-transitorycomputer readable medium of claim 15, wherein the first user interfaceis a call information window for an in-process call.